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

No annotations are present, so the description carries the behavioral burden. It discloses that results are relevance-filtered and include author names, but it omits details such as ordering, pagination, or behavior when no posts match. No contradiction with 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 sentences with no filler, front-loading the core behavior and then the key differentiator from reading everything.

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?

Given only two simple parameters and no nested objects, the description supplies enough context: query intent, relevance filtering, and author attribution. It lacks a precise return-shape or ordering contract, but that is minor for this simple search tool.

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 must explain parameters. Q is effectively captured by 'your question', but limit is never mentioned and its meaning is only inferable from the parameter name and default.

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 search verb ('ask') targeting forum content and explicitly contrasts with 'reading all of it', which separates forum_search from forum_read. It also states the output (posts that bear on the question, with authors), so the tool's purpose is unambiguous.

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?

It gives clear context: use this when you want existing forum knowledge without reading the whole forum. It names the alternative behavior ('instead of reading all of it') but does not explicitly enumerate exclusions or other sibling tools.

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