wordpress_get_post

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It merely states the action without revealing aspects like read-only nature, authentication requirements, error behavior, or what data the response contains. The term 'get' implies safety, but no explicit confirmation is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that immediately conveys the core purpose. However, it could be slightly longer to include essential parameter context without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a simple tool with two parameters and no output schema, the description should at least hint at the response structure and the effect of the context parameter. It fails to do so, leaving the agent to guess. The description is incomplete for an effective tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, yet the description adds no information about the parameters. While 'id' is self-explanatory, 'context' (with view/edit enum) is completely unexplained. The description should clarify that 'context' controls the amount of detail returned (e.g., edit returns more fields like raw content).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb (Get), resource (WordPress post), retrieval method (by ID), and scope (from configured site). It effectively distinguishes this tool from siblings like wordpress_get_page (for pages) and wordpress_list_posts (for listing multiple posts).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as wordpress_list_posts or wordpress_get_page. It does not mention any prerequisites, limitations, or the context parameter's role in determining the response format.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.