wordpress_get_post

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

With no annotations provided, the description carries the full disclosure burden. It usefully describes the return payload ('complete post data including content, metadata, and author information') since no output schema exists, but omits error conditions, authentication requirements, and rate limiting.

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?

Two well-structured sentences front-loaded with the action. The '[UNIFIED]' prefix is noise/metadata leakage but doesn't significantly impede readability. No redundant or wasteful content beyond that prefix.

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?

Adequate for a simple retrieval tool: covers the action and return value. However, given zero schema coverage and no annotations, the lack of parameter documentation and minimal sibling differentiation leaves notable gaps for agent understanding.

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 description coverage is 0%, requiring the description to compensate. While 'by ID' implicitly maps to post_id, it fails to document the 'site' parameter (format unclear) or 'fields' parameter (purpose unspecified), leaving two-thirds of the interface undocumented.

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?

Clearly states the action ('Get') and resource ('WordPress post') with scope ('specific...by ID'). The phrase 'by ID' implicitly distinguishes it from sibling tools like wordpress_list_posts, though it doesn't explicitly name alternatives.

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?

Provides implied usage context through the 'by ID' constraint, indicating use when a specific post identifier is known. However, it lacks explicit when-to-use guidance or contrasts with sibling tools like wordpress_get_page or wordpress_list_posts.

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