add_url_forward

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

With no annotations, the description explains the meaning of type, include_path, wildcard, and subdomain. However, it does not disclose side effects, permissions, or behavior beyond parameter documentation.

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 relatively short (4 sentences) and front-loads key facts. The last sentence about action is somewhat extraneous but not overly verbose.

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 7 parameters and no output schema or annotations, the description is insufficient. It does not cover all parameters, return values, error cases, or relationship to other tools.

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 0%, so description must add meaning. It explains 4 of 7 parameters (type, include_path, wildcard, subdomain) but leaves domain, location, and reason unexplained. The mention of 'action=URLFWD_ADD' adds minimal value.

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 the tool adds a URL forward, specifies the types (permanent/temporary), and explains key parameters. It distinguishes from sibling tools like delete_url_forward.

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 guidance on when to use this tool versus alternatives. The description lacks context about prerequisites, conflicts with other tools, or when not to use it.

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