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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive), and the description adds what they cannot: it takes no arguments, returns the catalog only, does not probe providers, does not consume the Toolweather check quota, and is free. Cost and side-effect disclosure of this kind is precisely the value structured annotations cannot carry.

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-loaded with purpose, trigger, and scope before the caveats, so the critical information lands first. The four negative clauses ('Do not use it as...') are individually justified but make the middle of the description long and slightly list-like rather than flowing.

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 output schema exists, but the description compensates by naming the returned fields (provider id, state, checked_at) and the possible state values. For a zero-parameter catalog tool with a fully covered safety annotation set, nothing an agent needs in order to call it correctly 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?

There are zero parameters, so the rubric baseline is 4. The description confirms 'No arguments', which is consistent with the empty schema and removes any doubt an agent might have about passing filters.

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?

Starts with a specific verb+resource ('List the AI and developer API providers Upstream tracks') and immediately states the payload (state and checked_at), which is exactly what an agent needs to know before calling it. It also names the sibling it feeds into (check_api_status), so it is distinguishable from the other list/check tools 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 a positive trigger ('Use to choose a provider id before check_api_status') and four explicit exclusions mapped to the correct alternatives (check_mcp_server_health, list_recent_api_changes, score_spend, check_merchant). The when/when-not/alternative triad is fully covered, leaving nothing to inference.

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