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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds behavioral context beyond annotations by explaining the ranking basis (identifier corrections) and the area-scoped vs global behavior. No contradictions 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 sentences front-load the core purpose first, then area scoping, then the prerequisite. There is no filler; each sentence contributes actionable guidance.

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 14-parameter tool with a fully described schema and an output schema, the description covers the high-level purpose, area-scoping rules, and prerequisite call. The schema supplies remaining parameter detail, and the output schema removes the need to document return values.

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 carries detailed per-parameter meaning; the description adds value by consolidating the three mutually exclusive area forms into one rule and stating the global-set fallback. It mostly re-frames schema content, hence not a 5, but the conceptual grouping is genuinely helpful.

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 lists taxa most often misidentified as a given taxon, ranked by identifier corrections — a specific verb and resource that distinguish it from siblings like inaturalist_get_species_counts or inaturalist_get_histogram. It does not explicitly name an alternative tool for contrast, so it stops short of a 5.

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 concrete when-to-use guidance: scope by exactly one area form (place_id, lat/lng/radius, or bounding box) or leave off for the global set, and the explicit prerequisite to resolve names via inaturalist_resolve_name first. It does not discuss when not to use this tool versus another, but the context is clear.

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