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

With no annotations, the description carries the burden of behavioral disclosure. It reveals ranking methodology (1–5 relative to reference variety), data source (documented tasting notes/trait spectra), and an existence threshold. It implies read-only query behavior, though it doesn't state side effects or error handling for missing guides.

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 dense but every clause contributes a distinct fact (ranking scale, invocation modes, existence condition). The example sentence aids clarity, though the long single-sentence structure could be more readable with clearer separation.

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?

There is no output schema or annotations, so the description must convey return shapes. It does so reasonably ('ranked answer', 'lists the uses', 'lists the species') and references the full guide URL via the limit parameter. It does not detail exact response formatting, but for a lookup tool this is adequate.

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 100%, but the description adds crucial combinatoric semantics not present in the schema: which parameter combinations yield which output shape, and that species alone or use alone return different kinds of lists. This is essential for correct invocation and goes beyond the schema.

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 states a specific verb (find best varieties), a clear resource (Farmdex tasting notes/trait spectra), and a concrete example ('best apple varieties for baking'). It also explains the ranking scale, which distinguishes it from sibling tools like search_farmdex or get_species.

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 explicitly defines three valid call shapes (species+use, species alone, use alone) and the condition under which a guide exists (minimum 3 documented varieties). It doesn't name specific alternatives, but the invocation patterns are clear enough to direct use.

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