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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description carries no extra behavioral burden. It adds no additional context about return values, error handling, or side effects beyond the basic operation, which is already covered by 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 a single, concise sentence with no redundancy. It is front-loaded with the essential information and contains zero wasted words.

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 getter with one well-defined parameter and annotations covering read-only behavior, the description is adequate. It does not explain return format, but no output schema is provided, and the operation's purpose is clear. It could mention what happens if the post is not found, but that is a minor gap.

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 0%, so the description should compensate. It does mention 'by id' (id ile), which clarifies that the 'id' parameter is the post identifier. However, it adds little beyond what the schema already defines with format and pattern, and does not explain the parameter's semantics in more depth.

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 verb (getirir - fetches) and the resource (single post by id). It distinguishes from sibling list_posts by specifying 'single' and 'by id', and from other getters (folder, idea) by naming '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?

Usage is implied: use this when you need a single post by id. However, the description does not explicitly mention alternatives or when not to use it, though the tool name and sibling context make it fairly obvious.

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