Search plants

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description correctly aligns with those. It adds useful behavioral context beyond annotations by noting that resolving a name costs an extra upstream request, which is important for an agent deciding whether to cache or reuse ids. Without output schema, it doesn't describe pagination or result limits, but with strong annotations, the bar is lower and it provides relevant cost information.

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, front-loaded with the verb and resource, and each sentence earns its place. The first sentence states purpose and output; the second provides essential usage guidance and a cost note. No fluff or redundancy.

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 the tool's moderate complexity (5 params, all documented in schema), the description covers the core value: search and return ids, plus a key behavioral note about cost. It doesn't discuss pagination or result structure, but without an output schema, that's not required. The description is complete enough for a search-list tool with strong annotations.

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%, so the schema already documents all five parameters with descriptions. The description adds little beyond the schema: it mentions 'search by name' but doesn't elaborate on the filter parameters. Per the rubric, since schema coverage is high, baseline is 3, and the description doesn't add extra value beyond the schema's parameter descriptions.

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 clearly states the tool searches the Perenual species catalogue by name and returns candidate species with ids. It distinguishes itself by mentioning that the returned id should be used with sibling tools (plant_details, companion_check, planting_window) rather than passing a name again, which highlights its role as a lookup step.

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?

Explicitly guides when to use this tool: to resolve a name into an id, and when not to: avoid passing a name to downstream tools. It names the specific alternatives (plant_details, companion_check, planting_window) and explains the cost of not using the id, providing clear exclusionary context.

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