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

With no annotations, the description carries the full burden. It discloses pricing per endpoint and global coverage, but omits critical behavioral aspects like output format, authentication requirements, rate limits, error handling, or whether the tool writes data. The 'data synthesis' phrasing hints at read-only aggregation but is not explicit.

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 organized as a bulleted list, which aids scanning, but the first line is a long run-on sentence and the text is truncated mid-sentence ('endangered s'). It front-loads the main purpose but lacks polish and completeness.

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 tool with 11 parameters, 9 endpoints, and no output schema, the description is insufficient. It lists endpoints but doesn't explain required parameters per action, sample requests, or response structure. An agent would struggle to invoke the tool correctly without additional context.

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% (all params have descriptions), but several descriptions are trivial (e.g., 'lat', 'lng', 'lang'). The description adds endpoint cost information but does not map endpoints to required parameters or explain how to use specific params per action. Baseline 3 is appropriate since the schema covers all params.

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's function as a global biodiversity intelligence API, synthesizing GBIF, IUCN, eBird, and iNaturalist data. It lists specific endpoints like species profiles, sighting reports, and migration tracking, which distinguishes it from sibling tools in other domains.

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?

The description implies usage for biodiversity-related queries through examples like species profiles and sighting reports, but it does not explicitly state when to use this tool versus alternatives or exclude other cases. No alternative tools are named.

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