create_forwarding_address

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

No annotations are provided, so the description carries the full burden. It discloses the destructive nature and gating requirements. However, it omits details like idempotency, rate limits, or authentication needs, leaving 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?

The description is concise at 6 lines, including a warning and API endpoint reference. Every sentence adds value, but the structure could be improved by separating the warning from parameter documentation.

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?

Given 11 parameters, 7 required, no output schema, and no annotations, the description is insufficient. It does not explain the return value, how to fill all required fields, or the full behavior of the confirm parameter. The tool's complexity demands more detail.

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?

With 0% schema description coverage, the description must compensate. It explains country_code and zip_code (including the request body field name for zip), but ignores most other required parameters (firstname, lastname, street, etc.) and optional ones (company, state, info, confirm). The mention of confirm is partial relative to its role.

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 clearly states 'Create a forwarding address (used as a forward target).' It uses a specific verb and resource, and distinguishes from sibling tools like get_forwarding_address.

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 highlights that the tool modifies the production account and requires double-gating (DROPSCAN_ALLOW_WRITES=1 and confirm=true), providing clear context. However, it does not explicitly mention when to avoid using it or list alternatives.

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