remove_alias

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

Describes removal and parameter options but does not mention behavior when both parameters are provided, or what happens if no parameters are given. No annotations to supplement, so description carries burden but leaves gaps.

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?

Efficient two-sentence description plus parameter list. No redundancy, front-loaded with purpose.

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?

Has output schema but description doesn't mention return values or success/failure. Lacks mention of reversibility or destructive nature. Adequate for simple tool but could be more 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?

Compensates for 0% schema description coverage by explaining each parameter's role (alias_names: list to remove; all_aliases: remove all). Adds meaning beyond schema types and defaults.

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?

Clearly states 'Remove Multipass aliases' with a specific verb and resource. Distinguishing from siblings like create_alias and list_aliases.

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?

Implies when to use (to remove aliases) but lacks explicit guidance on when not to use or alternatives. No sibling tool for removal, but context signals suggest no direct alternative.

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