manage_domain

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

Details each action and required fields, notes plain write and asymmetric defaults. Lacks output shape or error behavior, but adequate for a mutation tool.

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?

Concise, front-loaded main action, efficiently breaks down sub-actions with no filler.

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?

Covers essential aspects (scope, id source, actions, defaults). No output schema, but description sufficiently compensates for most use cases.

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 all 4 params; description adds meaning for action enum, conditional requirements, and asymmetric default warnings.

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 it dispatches a single domain management action, distinguishing from read-only siblings like list_domains and get_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?

Specifies required scope (domains:write), source of id (list_domains), advises checking state via get_domain_management, and warns about asymmetric defaults.

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