Remove Custom Domain

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

With no annotations, the description discloses an important behavior ('Cannot remove default domains') beyond the schema. However, it does not explain what happens when attempting to remove a default domain or other side effects, leaving some behavioral 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?

Two short sentences, front-loaded with the verb and resource, and no redundant information. Every word adds value.

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 one-parameter mutation tool, the description covers the core behavior and an important constraint. It could mention error handling or preconditions, but the simplicity of the tool makes this 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 covers the 'domain' parameter with a description, and coverage is 100%. The tool description adds context ('custom domain', 'allowed list') but no additional meaning about the parameter format or validation, so 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 'Remove a custom domain from the allowed list' – specific verb and resource. The additional constraint 'Cannot remove default domains' adds precision and distinguishes this from sibling tools like add_domain and 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?

Provides clear context for when to use (removing custom domains) and an exclusion ('Cannot remove default domains'), but does not explicitly mention alternative tools. The context is clear enough for an AI agent to select this tool for removal tasks.

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