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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that matching is semantic and can be based on a post or topic, but it does not explain behavior when no parameters are provided, when both post_id and query are given, or what output shape to expect.

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?

Two sentences, front-loaded with the core purpose and followed by practical trigger examples. Every sentence earns its place and there is no redundant filler.

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?

The combination of rich schema descriptions and safety annotations makes the basic call clear. However, the input schema marks all parameters optional and the description does not explicitly state that at least one of post_id or query should be provided, nor does it clarify precedence if both are supplied. Without an output schema, this leaves some ambiguity for correct invocation.

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%, so the parameters are already well documented in the input schema. The description mostly restates the two input modes ('reference post' and 'topic description') already present in the parameter descriptions, providing no additional semantic value.

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 uses a specific verb and names the resource: 'posts semantically similar to a reference post or a topic description.' This is clear and distinct from basic search, but it does not explicitly differentiate this tool from sibling tools like 'semantic_search' or 'recommend_posts,' which likely handle overlapping requests.

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 provides concrete trigger phrases: 'what else like this?', 'find related posts', 'show similar.' This gives clear context for when to use the tool, though it does not state exclusions or name alternatives when this tool should NOT be used.

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