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

Annotations already establish read-only, idempotent, non-destructive behavior; the description adds useful context beyond them: no authentication needed, the iNaturalist citizen-science data source, and the specific fields returned. There is 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?

Three tight sentences: purpose/examples, return payload and downstream use, and data source/auth. It is front-loaded and every sentence earns its place without redundant detail.

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 a well-described schema, an output schema, and annotations covering safety, the description supplies what remains essential: the search subject, examples, downstream tooling, and auth requirements. Nothing critical is missing for an agent to call it correctly.

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%, with all three parameters already described clearly. The description reinforces the query semantics with examples, but does not add material information about rank or per_page beyond what the schema provides.

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 opens with a specific verb and resource: 'Look up a species or other taxon by common or scientific name', with concrete examples. It also distinguishes itself from the observation-focused sibling tools by stating it returns taxon_id for use with inaturalist.observations_search and inaturalist.species_counts.

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 contextual guidance on how the returned taxon_id plugs into sibling observation tools, and states no auth is required. It does not explicitly state when not to use it or name alternatives, but the downstream-use note makes the intended role clear.

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