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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description adds real semantics annotations cannot convey: what all_verified means precisely (true only when ALL capabilities are verified) and the caveat that specs can still contain errors because untested capabilities exist.

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 core statement is front-loaded and the caveat/follow-up logic is ordered sensibly. It is slightly repetitive — the all_verified false case is restated in both the second and third paragraphs — but the extra lines still carry distinct information about untested capabilities.

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 no output schema, the description carries the burden of describing returns, and it does so with an explicit object shape and all top-level field names. It stops short of explaining fields like channels or docs_public, which leaves some interpretation to the agent.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly spends no words on inputs.

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 opening sentence gives a specific verb and resource ("Lists all providers") plus the salient attribute (verification status). It implicitly separates itself from search_specs/get_spec by being the enumerate-everything entry point, though it never explicitly says "use this to discover providers, use search_specs to filter."

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 concrete follow-up routing: when all_verified is false, "call search_specs or get_spec and check each capability's status." That is a genuine use-vs-alternative instruction, though it describes the drill-down path rather than when to pick this tool over search_specs in the first place.

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