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

Adds real operational context beyond annotations: always free, does not spend the daily quota, and refreshes every ~5 minutes. Annotations already cover readOnly/idempotent/openWorld, so the quota and freshness facts are the valuable additions. Return shape is described but no pagination behavior is needed for a fixed ~40-item list.

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?

Front-loads the core action and scope, then routes exclusions, then cost/freshness, then return shape. Dense but every sentence earns its place; no redundant restatement of the name.

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?

No annotations gaps and no output schema, so the description carries return shape, cost, freshness, and routing rules, which is everything an agent needs to invoke this list tool correctly. Nothing material 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?

Zero parameters, so baseline is 4. The description confirms 'No parameters', which is consistent and helpful, and it fully documents the returned fields even though that is technically output rather than parameter semantics.

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 precise verb (List) and resource (API providers ~40) with the exact fields returned. It distinguishes itself from check_api_status, list_recent_api_changes, and get_digest by name, so an agent can route without opening a schema.

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?

Gives explicit when-to-use (pick a provider id, one all-providers health pass) and explicit when-not (not for incidents, not for changes), naming the correct alternatives for each excluded case.

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