fix_app_icons

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

With no annotations, the description fully bears the burden. It states 'verify' but does not clarify whether the tool is read-only or if it modifies files. The name implies fixing, so the behavioral expectation is unclear.

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 very short, with an 'Args' section that is efficient. However, it lacks any explanation of return values or side effects, which would be valuable.

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 lack of output schema and the potential for destructive action (implied by 'fix'), the description is incomplete. It does not explain what happens on mismatch, what the return value indicates, or how to interpret results.

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%, so the description must compensate. It adds 'Path to .app bundle' for the single parameter, which is a minor clarification over the schema title 'App Dir'. This is insufficient for a parameter that likely requires validation.

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 states a specific action: 'Verify icon references in Info.plist match actual files in .app bundle.' This clearly identifies the tool's purpose, though the tool name 'fix_app_icons' suggests a repair action, creating a slight mismatch.

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?

No guidance is provided on when to use this tool versus alternatives like 'check_ios' or 'full_analysis'. There are no prerequisites, exclusions, or contextual hints for selection.

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