List relevant upcoming package changes, deprecations, additions and enhancements to user's systems.

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

Annotations already indicate read-only, idempotent, and open-world hints. The description adds value by detailing the return structure (meta and data fields) and explaining what a count of 0 means. No contradictions are present.

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 concise and well-structured: a short summary, a call-to-action, usage guidance, and a detailed output description. Every sentence adds value, and it is front-loaded with the most important 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?

Given the rich annotations and detailed output schema in the description, the description is complete. It covers purpose, usage, behavior, and return format without missing critical information.

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 have descriptions). The description does not add any additional meaning to the parameters beyond what the schema already provides. Baseline 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's function: 'List relevant upcoming package changes, deprecations, additions and enhancements to user's systems.' It specifies the verb 'List' and the resource, and distinguishes from the sibling tool 'get_upcoming_changes' by indicating when to use this one.

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?

Explicit instructions are provided: 'Use this tool to answer questions about upcoming package changes...' and 'Use this tool over get_upcoming_changes when the user asks about upcoming changes for their systems.' It also includes a 'CALL IMMEDIATELY' directive. However, it doesn't cover when not to use the tool explicitly.

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