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

Annotations only declare readOnlyHint and openWorldHint; the description adds the auth requirement (Bearer tt_…), billing model (credits vs. x402), free-tier rate limits, and the fact that the free result is limited with paid upgrade links. That is substantive behavioral context, though the x402/Apify pricing paragraph is more commercial than operational.

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?

Purpose and scope are front-loaded, but the middle is cluttered with billing mechanics (x402 via Apify, TidyTools credits) that don't help an agent decide or invoke, plus a dense rate-limit line. Some of it earns its place; the payment-channel detail does not.

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?

With one parameter, no output schema, and flat structure, the definition covers what the agent needs: scope, auth, rate limits, and a rough statement of what comes back (limited free result plus upgrade links). Only the exact shape of the enriched payload is left implicit, which is acceptable given no output schema exists.

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% and there is a single required parameter whose schema already gives the format ('One city with country code, e.g. Berlin, DE'). The description only restates 'one location', adding no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Names a specific verb ('Enriches') and resource ('one business listing in a city'), and immediately bounds the scope to a single location. The line 'Not for batch work or unrestricted monitoring' separates it from batch/enrichment siblings without ambiguity.

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?

'Use for one location. Not for batch work or unrestricted monitoring' gives explicit when-to-use and when-not-to-use conditions. It stops short of naming a concrete alternative sibling (e.g. a batch enricher), so it is clear context rather than full routing guidance.

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