axint.upgrade

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

Beyond the destructiveHint annotation, the description details the specific destructive effects: 'can run package installs, refresh Xcode wiring, and write .axint/upgrade; may use npm network'. It also mentions preservation of the current agent thread, adding valuable behavioral context.

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 front-loaded with the core purpose. It effectively uses bullet-like structure ('Use:', 'Effects:') to organize information. Slightly verbose with some redundancy ('Returns exact install commands' and mention of .axint/upgrade/latest.*), but still clear.

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?

The description covers all necessary aspects: purpose, usage condition, behavioral effects (destructive actions), and output mention. Given the existence of an output schema and comprehensive input schema, the description provides sufficient context for the AI agent to understand the tool's role and behavior.

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?

The input schema has 100% coverage with parameter descriptions, so baseline is 3. The description does not add additional meaning beyond the schema for individual parameters, but it does provide overall context for the 'apply' parameter's destructive nature.

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 action ('Check the latest Axint package and optionally apply the upgrade') and identifies the resource (Axint package upgrade). It distinguishes from sibling tools by noting it is not for app dependency upgrades and provides a specific use case: 'when axint.status shows a stale server'.

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?

Explicitly states when to use ('call when axint.status shows a stale server') and when not to use ('not for app dependency upgrades'), providing clear context for the AI agent.

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