Delete Allowed Domain

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

Beyond the annotations that already declare destructiveHint=true and openWorldHint=true, the description adds significant behavioral context: exact token permission requirements, delegate_to_contact_permissions handling, the confirm=true mutation guard, and possible side effects like sharing access, notifications, or provider charges.

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 front-loaded with the core action and uses headings and code formatting to organize permission details. It is longer than strictly necessary due to boilerplate side-effect language, but the structure keeps it readable and purposeful.

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 destructive, authenticated mutation with no output schema, the description covers the essential missing context: required permissions, delegated token behavior, confirm requirement, and potential side effects. An agent has enough information to invoke this correctly and safely.

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 coverage is 100%, so the baseline is 3, but the description adds critical invocation detail by explicitly requiring confirm=true for the mutation. It does not elaborate on the account parameter's meaning beyond the schema, so it exceeds baseline without fully covering all parameters.

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 opens with a specific verb and resource: 'Deletes an allowed domain from the account.' It clearly distinguishes itself from sibling tools such as create_allowed_domain, list_allowed_domains, and get_allowed_domain through its delete action and domain object.

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 establishes prerequisites like required API token permissions and confirm=true, which imply this is a privileged mutation. However, it does not explicitly state when to choose this tool over alternatives like create_allowed_domain or update tools, leaving usage context to inference.

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