funnels_create_redirect

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

Annotations indicate it is not read-only, not idempotent, and not destructive. The description adds nothing beyond the name, failing to disclose side effects (e.g., that it creates a persistent redirect that may affect traffic), permission requirements, or any operational nuances. With annotations already covering the basic safety profile, the description offers no additional value.

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?

A two-word phrase is not conciseness; it is under-specification. The description is too short to convey anything useful and fails to front-load important details. It provides no structure or helpful information.

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?

This is a creation tool with 5 parameters, no output schema, and no explanation of what a redirect is or how the tool behaves. An agent has almost no information to correctly invoke it beyond guessing parameter types. The description is completely inadequate for its complexity.

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 only 20% (only locationId has a description). The description does not explain any of the parameters, such as what 'action' values mean, how 'target' is used, or the format of 'path'. With such low schema coverage, the description was expected to compensate, but it provides zero parameter meaning.

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 'Create Redirect' states the action and resource, but it essentially repeats the tool name. It provides no details about what a redirect actually is, what it does, or how it differs from sibling tools like funnels_update_redirect_by_id or funnels_delete_redirect_by_id. This is vague and lacks any distinguishing context.

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 whatsoever on when to use this tool versus the other funnel redirect tools. No mention of prerequisites, typical use cases, or conditions that would make this tool preferable. The description is just a bare phrase with no context.

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