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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context: unrated providers are listed, scores are computed from dated/sourced data points, and without a product each provider shows its best standing. No contradiction exists.

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 is three dense sentences with no filler. It front-loads the core purpose, then covers filtering behavior, computation methodology, unrated providers, and the sibling alternative. Every sentence earns its place.

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 an output schema present, annotations covering safety profile, and no required parameters, the description is complete enough for a listing tool. It covers default product behavior, unrated providers, and the single-provider alternative without needing to restate return fields.

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 60%, and the description partially compensates by explaining product-absence behavior and mentioning the product/tier/profile filter dimensions. However, it adds little semantic value for limit and locale, which remain mostly self-explanatory or covered by schema defaults.

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 verb 'List', names the resource 'providers of banking for international clients', enumerates the fields shown, and explicitly differentiates from bank_rating. An agent can immediately understand what this tool returns and how it differs from its 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 description explicitly directs users to bank_rating 'for one provider with its evidence', providing a clear alternative for a different use case. It also explains the default behavior when no product filter is supplied, which is valuable usage guidance.

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