get_post

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

The description 'Get a single post by ID' aligns with the readOnlyHint annotation, confirming it is a read operation. No additional behavioral traits (e.g., permissions, rate limits, response structure) are disclosed, but the annotation already covers the safety profile, so the description adds minimal extra value.

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 sentence with no extraneous words. It is concise and front-loaded with the essential 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?

Given the tool's simplicity (single parameter, no output schema, read-only), the description is adequate. It states the core functionality. However, it does not specify the return format (e.g., the post object), but this is often assumed from the tool name and common REST patterns, so it is nearly 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?

The input schema has one parameter (postId) with a description ('The post ID'), giving 100% coverage. The description adds no further meaning beyond what the schema already provides, so baseline 3 is appropriate.

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 (a single post), and the method (by ID). It is specific and distinct from sibling tools like list_posts (retrieves multiple) and other get_* tools (different resources).

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 use when you have a specific post ID, which is clear context. However, it does not explicitly mention when not to use it (e.g., use list_posts for multiple posts) or provide alternatives, but the purpose is straightforward enough for an AI agent.

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