get_post_by_id

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

Discloses read-only nature and return shape, but with no annotations, additional details like idempotence or side effects are not explicitly stated, though implied.

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?

Four sentences, front-loaded with key info, no wasted words. Efficiently conveys purpose, usage, return, and alternatives.

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?

With single parameter well-explained, return shape described, and correct differentiation from siblings, the description is complete for a simple tool.

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%, but description adds value by clarifying the parameter type (numeric integer), providing an example, and explaining its use context.

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 explicitly states it is a read-only, strict-typed variant that accepts only a numeric post id, clearly distinguishing it from get_post and get_post_content.

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 explicit guidance: use when caller has integer id for type safety and fewer round-trips; use get_post for slug-or-id input and get_post_content for post body.

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