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

With no annotations, the description carries the burden; it does add real behavior by disclosing the sort order (soonest first), which the schema cannot express. However, it says nothing about whether results are bounded/truncated, what a missing provider match does, or the record shape returned for a 2-param read tool.

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?

A single sentence that front-loads the action, resource, scope and ordering with no filler. Nothing is padded.

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 tool with zero annotation coverage, no output schema and an entirely undocumented parameter schema, the one-line description is thin. An agent cannot tell how the provider filter behaves or whether the result set is capped before calling it.

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 0%, so the description must compensate and it largely fails: 'next N days' hints at the days parameter but omits its default (30) and the 1–3650 bounds, and the provider parameter is not mentioned at all, leaving its matching semantics (exact name? substring?) completely undefined.

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 specific verb ('List'), resource ('AI model shutdowns'), time scope ('next N days') and ordering ('soonest first'), so the agent knows exactly what it returns. It does not name any sibling for contrast, but the resource is distinct enough from search_models or get_shutdown_date that confusion is unlikely.

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?

Usage is only implied — an agent can infer this is the tool for upcoming shutdowns, but nothing states when to prefer it over get_changes_since or get_shutdown_date, nor any preconditions. No alternatives or exclusions are named.

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