email_forwarder_create

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

With no annotations, the description must carry the behavioral burden. It only reveals that this is a create operation and mentions 'confirm: Required,' but does not disclose side effects, permission needs, idempotency, or what happens to an existing forwarder. The confirm statement also conflicts with the schema, where confirm is optional and defaults to false.

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 compact and front-loaded: one clear purpose sentence followed by a terse argument list. It contains no filler, though the argument explanations are minimal.

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 simple 5-parameter creation tool with an output schema, the description is borderline adequate. It lacks key context such as what an email forwarder does, when confirmation is required, and any preconditions, but the core parameters are at least named.

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?

The schema has 0% description coverage, so the description must compensate, and it does explain most parameters: 'user: Local part (source)', 'destination: Destination address or comma-separated list', and 'impersonate: Owning user' add real meaning. However, 'domain: Domain' adds little, 'confirm: Required' contradicts the schema, and no formats or constraints are provided.

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 an email forwarder,' which identifies the exact verb and resource. It does not distinguish itself from sibling tools like email_forwarders_list or email_forwarder_delete, but the action is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of when creation is appropriate. The description simply states the operation without contextual cues.

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