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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: results are ranked by relevance, and it discloses the return shape (slug, title, summary, a Bayesian 0-100 score, report counts) which is valuable since no output schema exists.

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 search action and modalities, then the return fields. Dense and largely waste-free; the return-field enumeration is long but earns its place because there is no output schema.

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 five-parameter, zero-required, no-output-schema search tool, the description covers what it matches on, how results are ranked, and what comes back. Missing only the behavior with no arguments at all and any pagination/total-count guidance, which are minor given the limit parameter and defaults live in the schema.

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 coverage is only 40%, so the description must compensate. It usefully extends the query parameter (schema says only 'Keywords') to also accept a plain-language question, and confirms category/tag filtering, but it never explains sort or limit semantics, leaving two of five parameters undocumented.

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?

States a specific verb (search) and resource (BotGathering recipes) and enumerates the search modalities: keywords, plain-language question, category, tag. It does not explicitly differentiate itself from siblings like get_recipe or ask_how_to, but the 'find without a slug' framing is clear enough to separate it from the lookup 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?

Usage is implied rather than stated: the mention of 'keywords or a plain-language question' suggests this is the discovery entry point, and the sort enum option 'needs-testers' hints at a tester-seeking use case. No explicit when-to-use, when-not-to-use, or named alternative (e.g. get_recipe once a slug is known, ask_how_to for how-to questions) is given.

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