get_post

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior. Beyond that, the description adds useful detail about the returned payload: media, published ids, and any error. It does not describe auth requirements, not-found behavior, or pagination, but for a simple get-by-id tool it adds meaningful context beyond annotations.

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 two short sentences and front-loads the core operation. The first sentence ('Get a post.') is slightly redundant with the tool name and title, but the second sentence efficiently adds return-content detail.

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 read tool with annotations covering safety and no output schema, the description is largely complete because it explains the key returned contents. It could be more complete by mentioning lookup-by-id or error conditions, but the essential context is present.

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 100%, with the sole 'id' parameter documented as a numeric id. The description does not mention the parameter at all, so it adds no meaning beyond the schema; 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 states a specific verb and resource ('Get a post') and clarifies the scope as one post rather than a list, which distinguishes it implicitly from list_posts. It does not explicitly name a sibling alternative, but the singular scope makes the purpose clear.

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?

Usage is only implied: retrieving a single post by its id, with list_posts presumably used for listing. There is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives such as list_recent_posts.

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