wp_get_post

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

The description states 'Read-only', which is an important behavioral trait. However, with no annotations provided, the description carries full burden for transparency. It could add more details like no side effects or error behavior, but for a simple retrieval tool, this is adequate.

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 extremely concise: one sentence conveying both purpose and behavioral trait. It is front-loaded with the main action and resource, and every word serves a purpose with no extraneous text.

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 tool with one parameter and no output schema, the description covers the key aspects: what it does, how it's identified (by ID), and a behavioral note (read-only). It could mention the return format (e.g., returns post object) but overall is quite complete.

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 100% for the single parameter 'id', with description 'Post ID'. The description adds 'by ID' but no additional meaning or constraints beyond the schema. The baseline is 3, and no extra value is added.

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 action 'Get', the resource 'single WordPress post', the method 'by ID', and the scope 'full content'. It also indicates it is read-only, which distinguishes it from sibling tools like wp_create_draft_post or wp_list_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 implies usage when needing a single post by ID, but provides no explicit when-not-to-use guidance or direct comparison to sibling tools like wp_search_content or wp_get_page. The context is clear but lacks explicit exclusions.

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