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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: results are ranked across all providers, pricing is per request and per record with a cap, and the data source is provider-published OpenAPI deprecation markers. It does not describe response fields, but no output schema exists and the ranking statement implies the core return shape.

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 dense but efficient: it front-loads the core purpose, then adds usage context, the drill-down alternative, and pricing. The statistics and pricing URL are arguably optional but relevant for a paid catalog view, so no sentence is wasted.

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 paginated, paid, read-only catalog tool with no output schema, the description covers purpose, ranking, alternatives, and cost. It would be more complete with an explicit statement of the response format or fields, but the ranking description and schema constraints make invocation feasible.

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 only 33%: context is well described, but page and limit have no textual descriptions. The tool description does not compensate for page/limit semantics; it only obliquely references per-record pricing. The agent must rely on conventional meaning of pagination parameters, which is a real gap for low coverage.

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 a specific resource and action: every provider publishing at least one deprecated operation in its own OpenAPI, ranked by count. It clearly differentiates this catalog-level view from per-provider drill-down tools by noting that a provider's own deprecated filter requires you to already suspect the provider.

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 explicitly explains when this tool is valuable ('which nothing could see before') and names the alternative drill-down path: get_provider_operations(deprecated=true). This gives the agent a concrete routing rule between siblings.

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