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

No annotations are provided, so the description carries full behavioral burden. It discloses the default window (90 days) and the sort order, which is useful, but says nothing about read-only nature, return shape, whether replacements are included despite the banner mentioning '替代' (replacement), or behavior when days is omitted or zero.

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 efficient sentence with the topic label front-loaded in brackets. No filler, though the bracket label slightly duplicates the rest of the sentence.

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 simple one-parameter list tool with no output schema and no annotations, the description covers the default and sort order, which is the minimum viable set. It still leaves the sibling-overlap question and return contents unresolved.

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 0% — the single 'days' property is an undescribed number. The description partially compensates by stating the default is 90 days and that it is a day-count window, but it gives no units caveats, bounds, or behavior for explicit values.

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 gives a specific verb and resource ('lists AI models that will be shut down within N days, sorted by shutdown date'), so an agent knows exactly what it returns. However, it never distinguishes itself from the near-identical sibling models__ai_model_shutdown_calendar, which appears to cover the same domain, leaving the agent to guess which one to call.

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 guidance, no exclusions, and no reference to the closely related models__ai_model_shutdown_calendar sibling. The only implied usage is that it is a time-windowed lookup, which is inferred from the parameter rather than stated.

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