wordpress_get_post

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

No annotations are present, so the description carries the burden. 'Get' implies read-only, and 'full content' indicates return scope. Missing details on error handling or nonexistent IDs, but adequate for a basic read tool.

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 compact with a clear one-line summary followed by concise Args and Returns sections. No filler words or redundant information.

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?

For a simple single-param getter with an output schema, the description covers the essential purpose and parameter. Output schema handles return values, so the lack of edge-case discussion is acceptable.

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?

Schema coverage is 0%, so description must compensate. It explicitly identifies post_id as 'Post ID' and the main line clarifies it refers to the WordPress post ID, adding meaning beyond the raw schema.

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 it retrieves a single WordPress post by ID with full content. The verb 'Get' combined with 'single' and 'by ID' distinguishes it from sibling tools like list/search and page tools.

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?

It clearly implies use when you have a specific post ID and need full content. However, it does not explicitly mention alternatives like wordpress_list_posts or wordpress_search_posts, so it lacks explicit exclusions.

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