axint.upgrade

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

Description adds details beyond annotations: destructive effects when apply=true (package installs, refresh Xcode wiring, write .axint/upgrade, may use npm). No contradiction with annotations.

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?

Well-structured with front-loaded purpose, then usage, inputs, effects. Slightly long but each sentence adds value.

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 tool with 7 params and destructive behavior, the description covers purpose, usage conditions, parameter roles, and effects. Output schema exists but not needed in description.

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 100%, so baseline 3. Description adds value by grouping parameters (e.g., 'matter only when applying') and noting defaults (apply defaults false).

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 verb 'Check' and 'apply', the resource 'Axint package', and distinguishes from sibling tools by specifying 'not for app dependency upgrades'.

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 tells when to call: 'when axint.status shows a stale server' and what not to use for: 'not for app dependency upgrades'.

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