homebutler

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

With no annotations provided, the description carries full behavioral disclosure burden and successfully communicates destruction scope: containers are removed but data persists. However, it omits details about stopping behavior (graceful vs force), reversibility, or error scenarios when the app is not found.

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 two-sentence structure efficiently delivers the core action and critical behavioral constraint without redundancy. Every element earns its place, with 'Data is preserved' providing essential safety information for a destructive operation.

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?

For a single-parameter tool with no output schema, the description adequately covers the operation's intent and side effects. It could be improved by mentioning prerequisites (app must be installed) or return value indicators, but is sufficient for tool selection.

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?

The schema coverage is 100% with the parameter described as 'App name' in the schema, providing complete technical documentation. The description adds no additional semantic context about the parameter, meeting the baseline for high-coverage schemas.

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 uses specific verbs 'Stop' and 'remove' targeting 'containers' of an 'installed app', clearly indicating an uninstallation operation. It distinguishes itself from sibling tool 'install_purge' by explicitly noting that 'Data is preserved', implying the latter removes data.

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?

While the phrase 'Data is preserved' implicitly suggests when to use this tool (when retention is desired) versus 'install_purge', it lacks explicit guidance such as 'Use this to uninstall while keeping data; use install_purge to remove data as well'. No prerequisites or error conditions are mentioned.

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