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

Beyond the read-only and open-world annotations, the description discloses important operational behavior: free-result limitations, paid upgrade links, x402 payment handling, Authorization bearer requirements, credit billing, and detailed daily rate limits by IP, shared pool, and global cap.

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 purpose is front-loaded in the first sentence, and the remaining sentences cover usage, billing, authentication, and rate limits without excessive waste. The structure is slightly dense and mixes several operational details, but it remains appropriately sized.

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 one-parameter read-only tool with full schema coverage and annotations covering safety, the description supplies the missing practical context: usage boundaries, authentication, billing behavior, and rate limits. No output schema exists, and the description adequately indicates that results may be limited unless upgraded.

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%, and the single parameter is already well documented in the schema with format guidance. The description reinforces the one-location constraint but does not add syntax or format detail 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 clearly states a specific verb and resource: it returns one business listing in a city. It also scopes the tool to a single location and explicitly excludes batch work, though it does not name a particular sibling tool as the alternative.

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 usage context ('Use for one location') and exclusions ('Not for batch work or unrestricted monitoring'). It does not explicitly route the agent to a named alternative sibling tool, so it falls short of the top score.

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