shannon_uninstall

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

No annotations provided. Description explicitly states the destructive action (stop runtime and remove home directory) and mentions the confirmation token. Lacks details on how 'clean' affects volumes/network and post-uninstall state, but adequately discloses core behavior.

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?

Two concise sentences with no unnecessary words. Information is front-loaded: action, target, precondition.

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 no output schema, the description covers the main purpose and prerequisites. It could mention expected outcome or return format, but for a destructive uninstall tool, the current level is adequate.

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 100%, so the description adds little beyond what the schema already provides. It reinforces the confirmation token requirement, but that is already in the schema. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Stop' and resource 'Shannon runtime' and 'remove ~/.shannon'. It distinguishes from siblings like shannon_stop which likely only stops without removal.

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 explicit guidance on when to use this tool versus alternatives like shannon_stop. The only hint is the requirement for a confirmation token, which is not a usage context but a precondition.

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