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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only lookup but never states matching semantics (content vs. title vs. tag), result ordering, pagination, or what a result entry contains; the useful 'returns at most 50-100 matches' detail lives in the parameter schema, not the description.

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?

A single sentence that front-loads the scope and appends the workflow cue. No filler, no restatement of the title, every clause earns its place.

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?

With four fully documented parameters and a low-complexity read operation, the definition is largely sufficient to invoke correctly. The remaining gap is search semantics for a tool with no output schema and no annotations -- the agent still cannot predict result shape or ranking.

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% -- query, tag, branch and limit all carry their own descriptions, including the #tag exact-match rule and the limit caveat. The description adds no syntax, format, or interaction detail beyond the schema, so the baseline 3 applies.

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?

It names a specific verb and resource ('Search Fork's improvements, questions and blog posts') and constrains the query form ('by keyword or #tag'). That is enough to separate it from get_post (single fetch), get_feed (browse) and the post_* creation tools.

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 gives a concrete when-to-use trigger: 'check here before posting something new, in case the fix already exists.' It does not, however, mention any alternative when the agent has no intended post, or contrast with get_feed/list_branches for browsing, so no exclusions are stated.

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