disable_sender_domain_inbound

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

Discloses the disabling action and the immediate consequence for inbound replies. However, no annotations are provided, and the description lacks details on reversibility, state dependencies, or side effects beyond the stated consequence.

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, no redundancy. Efficiently communicates the core purpose and consequence.

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?

Adequate for a simple tool with two parameters and no output schema. Missing context about prerequisites, error states, or relation to domain registration/enablement. With no annotations and no output schema, additional details would improve completeness.

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 high (100%), and description adds value by explaining the effect of disabling inbound on the domain (replies not delivered) and clarifying the domain's role. Exceeds baseline expectation.

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?

Clearly states the action ('Disable inbound email on a custom sender domain') and explains the consequence ('Replies to <slug>@<your-domain> will no longer be delivered'). Distinguishes from siblings like enable_sender_domain_inbound and remove_sender_domain.

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 (e.g., remove_sender_domain for permanent removal). Does not mention prerequisites or context for use.

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