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

Annotations only declare readOnly and openWorld; the description adds substantial context beyond that: data source (clio.com/app-directory), residential proxy, and bluntly states the cost model ($0.01 USDC per successful call via x402 on Base/Solana/Arc, failed calls free). That payment detail is critical and impossible to get from structured fields.

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?

A single dense paragraph, but it is front-loaded with the resource and field list before the operational details. Every clause (fields, source, pricing) carries weight, though it could be broken into sentences for scannability.

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?

Even though an output schema exists, the description fully covers source, pagination, returned fields, and pricing. Nothing an agent needs to decide to call or how to interpret cost is missing.

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% (page range 1-60 with default), so baseline is 3, but the description adds genuinely new meaning by specifying one page of 9 items and that a total page count is returned, which clarifies pagination behavior beyond the raw schema.

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?

States a specific resource (Clio App Directory), enumerates the exact fields returned (slug, name, description, price, logo, link, page count), and frames it as a one-page-of-9 listing. An agent knows precisely what it fetches and it is clearly distinct from the many company/registry siblings.

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 data scope implies usage but there is no explicit when/when-not guidance or reference to alternatives. For a niche-specific directory with no real sibling overlaps this is tolerable, but the agent is left to infer that this tool is only for Clio integration data.

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