Get Domain Forwarding

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description indicates a read-only 'Get' operation, which is a useful behavioral hint. However, it does not disclose what the response contains, how errors are handled, or any side effects (if any). Since it is a simple getter, this minimal disclosure is adequate but not rich.

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 a single, concise sentence that is front-loaded with the key information. It contains no filler or redundant wording, making it highly efficient.

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?

The tool is simple (one parameter, no output schema, no annotations). The description adequately states the core action. However, without an output schema or additional explanation, the agent cannot infer the return structure or potential edge cases, leaving some gap in 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 description coverage is 100% (the only parameter 'domain' is described as 'Domain name'). The description adds no additional meaning beyond the schema, which is already clear. Baseline for high coverage is 3, and the description does not compensate further.

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 'Get forwarding config for a domain' uses a specific verb ('Get') and resource ('forwarding config') with a clear scope ('for a domain'). This distinguishes it from sibling tools like domains_update_forwarding and domains_delete_forwarding, which are clearly different operations.

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 the tool's usage: retrieve forwarding configuration for a domain. However, it does not explicitly state when to use this over alternatives or mention any preconditions. No alternative tools are referenced, and no exclusions are provided.

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