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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered elsewhere. The description adds real value beyond that by describing each record's payload (certainty, scope, required action, replacement guidance, official source) and stating the result ordering, which tells the agent what the data can be trusted for.

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?

One front-loaded sentence that opens with the resource and closes with the ordering rule, with no filler. The parenthetical provider list is long but carries genuine coverage information, so it mostly earns its place.

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 usefully enumerates the returned fields, which is exactly the missing context an agent needs to interpret results. It would be a 5 if it defined the possible values of 'certainty' and 'scope' or explained how this differs from the closely related list_ai_shutdowns sibling.

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 coverage is 100%, with every parameter self-documenting, including the status enum and the limit default. The description contributes only the 'Upcoming first' ordering and provider breadth; it adds no semantics for query matching (e.g. whether it is substring or exact) beyond the schema's own example.

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 names a specific resource (model retirement and shutdown deadlines) and enumerates the covered vendors (OpenAI, Anthropic, Azure OpenAI, Bedrock, Vertex, Mistral, xAI, DeepSeek), so an agent knows exactly what domain it queries. It falls short of a 5 because it never distinguishes itself from the sibling list_ai_shutdowns, which appears to overlap substantially.

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?

There is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives such as list_ai_shutdowns or find_model_changes. The only usage signal is the implicit 'Upcoming first' ordering and the default status, which an agent must infer from the schema rather than the prose.

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