package-remove

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

Discloses domain reload and package resolution triggers, which are significant behavioral traits. Lacks details on permissions or reversibility but is thorough given no 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?

Concise, front-loaded with core action, followed by important notes in a clear and structured manner with no wasted words.

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?

Covers constraints and recommended workflow adequately for a removal tool without output schema. Could mention return or effect on dependencies, but overall complete.

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?

Adds value by clarifying packageId format (no version number) and example, but requestId remains undocumented. Schema coverage at 50% leaves room for improvement.

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?

Describes a specific action (remove/uninstall) on a specific resource (package from Unity project), and clearly distinguishes from siblings like package-add and package-list.

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 not to use (built-in or dependency packages) and recommends using package-list first, providing clear guidance on tool selection.

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