recent_lifecycle_changesLifecycle state changes across all tracked providers, newest first. Use this to answer 'what model deprecations happened recently?'.
| Name | Required | Description | Default |
|---|---|---|---|
| provider | No | Restrict to one provider. | |
| sinceDays | No | Look back this many days. Defaults to 30. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds that results are ordered newest first and cover all tracked providers, which provides useful behavioral context beyond annotations without contradiction.
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?
The description is extremely concise: one sentence stating the tool's function and ordering, plus a usage hint. No unnecessary words, front-loaded with key information.
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 list tool with two well-documented parameters and readOnlyHint/openWorldHint, the description covers purpose and ordering. However, it does not describe the output format (e.g., fields like provider, model, date, change type), which could be a minor gap.
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 100%. Both parameters ('provider' and 'sinceDays') are described in the schema. The description does not add additional meaning beyond the schema, so a baseline score of 3 is appropriate.
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 clearly states the tool lists lifecycle state changes across all providers, ordered newest first, and provides an example query ('what model deprecations happened recently?'). This distinguishes it from siblings like list_retiring_models (retiring only) and check_model (single model).
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?
The description includes a specific usage example ('Use this to answer...'), giving clear context. However, it does not explicitly mention when not to use the tool or suggest alternatives among siblings, such as list_retiring_models for retirement-specific queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: check_model validates a specific model ID, list_retiring_models shows upcoming retirements, recent_lifecycle_changes shows recent events, search_models allows filtered queries, and suggest_replacement provides alternatives. No overlap.
Most tools follow verb_noun pattern (check_model, list_retiring_models, search_models, suggest_replacement), but 'recent_lifecycle_changes' uses an adjective instead of a verb, breaking the pattern slightly.
With 5 tools, the server is well-scoped for its domain of model lifecycle management. Each tool addresses a core need without unnecessary bloat.
The tool set covers key lifecycle tasks: checking status, listing retirements, recent changes, searching, and suggesting replacements. Minor gaps exist (e.g., no tool to view all models without filtering, but search_models with no filter achieves that).