biopulse

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

No annotations are provided, placing the full burden on the description. It does not disclose data freshness, authentication requirements, rate limits, or effects of incorrect parameters. Endpoint costs are mentioned but are not behavioral.

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 contains a clear first sentence but then includes cluttered formatting (prices, emojis, bullet list) and redundant coverage line. It could be more concise and front-loaded with essential information.

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 11 parameters, no output schema, and multiple endpoints, the description lacks guidance on parameter dependencies (e.g., which are needed for each action). It does not explain what each endpoint returns or how to choose between parameters like 'dist' and 'radius'.

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?

While schema coverage is 100%, many parameter descriptions are tautological (e.g., 'lat', 'lng', 'lang', 'location' just repeat the name). The tool description adds no additional context for these parameters. The 'action' enum is well-described, but overall parameter semantics are poor.

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 provides a global biodiversity intelligence API synthesizing GBIF, IUCN, eBird, and iNaturalist data, and lists specific endpoints like species profiles, sightings, and conservation status. This distinguishes it from unrelated sibling tools.

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?

No explicit guidance on when to use this tool versus alternatives. The description lists many sibling tools but provides no criteria for selection. The intended use for biodiversity queries is implied but not spelled out.

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