get_post

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

No annotations are provided, so the description itself must convey behavior. It clearly indicates a retrieval operation ('Retrieve'), which is transparent. However, it does not disclose potential error conditions (e.g., non-existent ID) or any side effects. For a simple read tool this is acceptable but minimal.

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, focused sentence that conveys the exact purpose with no filler. It is optimally concise.

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 one-parameter get operation with no output schema, the description is sufficient. It covers what the tool does and the key input. It lacks explicit mention of response format, but that's often inferred.

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 already provides 100% coverage for the single 'id' parameter, including its type and meaning. The description adds 'by its ID', which rephrases the schema without adding new meaning. Baseline 3 is appropriate since the schema dominates.

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 tool retrieves full details and prompt of a specific post by ID. It uses a specific verb ('Retrieve'), specifies the resource (post), and narrows scope ('specific post by its ID'), distinguishing it from sibling tools like list_posts or update_post.

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 you have a post ID) but does not explicitly mention when to prefer this over alternatives like list_posts or when not to use it. It lacks explicit 'when to use vs when not' guidance, so the agent must infer the context.

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