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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the ranking mechanism (posts with most tag overlap), which is useful behavioral context beyond annotations. It does not contradict 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?

One sentence, front-loaded with the input condition and action, zero filler. Efficient and scannable.

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 description covers core functionality but omits the return value shape (no output schema) and the behavior/semantics of the optional 'limit' parameter. Given low complexity and annotations that cover side effects, this is adequate but not 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?

With 50% schema description coverage, only the 'url' parameter has schema documentation. The description restates the URL input but adds no new meaning, and the 'limit' parameter is entirely undocumented in both schema and description. The description fails to compensate for the missing limit semantics.

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?

Description states a specific verb 'find' with resource 'other posts that share the most tags with it', clearly distinguishing this from siblings like search_posts (text search) and browse_by_tag (single-tag filter). The algorithm (tag overlap) is explicit, so an agent can tell when this is the right tool.

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 a post URL is available and related content by tag similarity is needed, but it does not explicitly name alternatives or exclusion conditions. No guidance on when to prefer related_posts over search_posts or browse_by_tag is given.

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