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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that only models with an 'exact' shutdown date are included (implying estimated/unknown dates are excluded), and 'List' signals a read-only operation, but it says nothing about defaults, ordering, or result limits.

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, front-loaded sentence with no filler. It is efficient, though its terseness contributes to the missing parameter and usage guidance rather than being a model of structure.

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 annotations, no output schema, and 0% parameter documentation, the description leaves substantial gaps: the meaning of the 'provider' filter, the default value of 'days' when omitted (0 required parameters), and what the returned model records contain.

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% for two parameters. The description only indirectly explains 'days' as N; the 'provider' parameter is never mentioned, so an agent must guess its role (filter? exact match? case sensitivity?). It does not compensate for the coverage gap.

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') and resource ('models') with a clear qualifying condition (an exact shutdown date within the next N days). An agent can tell what it returns, though it does not explicitly contrast itself with siblings like check_model or migration_diff.

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 by the 'next N days' phrasing. There is no explicit statement of when to reach for this versus check_model or migration_diff, and no mention of prerequisites or exclusions.

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