stape_remove_domain

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

With no annotations, the description must disclose behavioral traits itself. It only states the action 'remove,' which implies destruction, but does not mention permanence, permissions, or side effects such as whether the domain must be detached from any containers first or if the action is reversible.

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?

A single, grammatically correct sentence that directly states the tool's purpose without redundancy or filler. Every word contributes to meaning.

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 simple removal tool with complete parameter schemas, the description is adequate but lacks contextual details like irreversibility or prerequisites. Given there is no output schema or annotations, the description leaves the agent without full behavioral context, but the simplicity of the operation keeps it from being severely incomplete.

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 provides 100% description coverage for both parameters, so the baseline is 3. The tool description does not add any additional meaning beyond what the schema states, but it does not need to given the schema's completeness.

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 a specific verb ('remove') and identifies the resource ('custom domain') and scope ('from a Stape container'), clearly distinguishing this from sibling tools like stape_add_domain and stape_list_domains.

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?

The description implies when to use the tool (when you need to remove a domain), but provides no explicit guidance on alternative tools or exclusions. It does not mention when not to use it or prerequisites, leaving usage inferred rather than stated.

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