allstats_search

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

No annotations exist, so the description carries the full burden. It discloses high latency due to proxy/scraping, states no API key is required, and frames it as a fallback due to speed. It doesn't mention rate limits or result structure, but covers the most critical operational constraints relevant for an agent.

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?

Two sentences, purpose first, then a clearly marked IMPORTANT caveat. Every clause adds value—no filler or redundant 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 the 8-parameter schema with thorough descriptions and no output schema, the description provides the essential context: scope, content types, latency warning, and relationship to the faster 'search' tool. It doesn't explain return values, but that's not expected without an output schema. Covers operational caveats well, though it could mention potential scraping fragility.

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 every parameter having a description. The description adds a high-level mapping by listing content types, but doesn't add new syntax or format details beyond the schema, so the baseline 3 is appropriate.

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 'Search BPS content via AllStats Search Engine' and enumerates content types (publications, tables, press releases, infographics, microdata, glossary, classifications), clearly identifying the tool's scope. It also differentiates from sibling 'search' by positioning this as a fallback, making the purpose clear and distinct.

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 instructs to use the 'search' tool first, stating it is 'much faster', and to only use this tool if 'search' finds no results. This provides clear when-to-use and alternative guidance, leaving no ambiguity about when this tool should be invoked.

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