uninstall_skill

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

With no annotations, the description must carry behavioral disclosure. It does state the primary effect (removing the skill from the import record) and a non-effect ('Shelf unchanged'), which is useful. However, it omits other behavioral traits like reversibility, permissions, or side effects on linked resources.

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 two short sentences with no filler: the main action is front-loaded and the second sentence adds a meaningful scope qualifier. Every word earns its place.

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?

Despite having an output schema, the overall definition is incomplete for a mutating tool with five required, undocumented parameters and no annotations. It relies heavily on undefined domain jargon like 'this map' and 'Shelf,' and offers no information about prerequisites, failure modes, or the broader uninstall workflow.

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 description coverage is 0%, so the description must compensate for the five undocumented required parameters. Phrases like 'this pack skill' and 'this map' only vaguely map to pack, skill_id, project, and working_folder; version is not addressed at all.

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 clear action ('Drop') and a specific resource ('this pack skill') plus a scope ('this map's import record'). The phrase 'Shelf unchanged' helps distinguish it from deletion-like operations, though it does not explicitly name a sibling tool.

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?

There is no guidance on when to choose this tool over alternatives such as unlink_skill, delete_skill, or install_skill. 'Shelf unchanged' implies a contrast, but no explicit when-to-use or when-not-to-use information is provided.

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