Raw Action1 API request (escape hatch)

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description goes further and names the exact gates required for writes: ACTION1_ALLOW_DESTRUCTIVE, confirm:YES, dry_run defaulting to true, plus ACTION1_ALLOW_ACCOUNT_OPS for account operations. That is concrete, non-obvious operational context an agent cannot infer from annotations alone.

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?

Two sentences, front-loaded with the escape-hatch purpose before the gating rules. Every clause carries decision-relevant information (when not to use it, which verbs are free, what the write path requires).

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 7-parameter arbitrary-passthrough tool with an output schema, the definition covers safety gating and routing well. It stops short of telling the agent how to discover valid paths or how errors/pagination surface, which would matter for a truly open-world escape hatch.

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 100%, so the baseline is 3; the description earns above that by explaining how parameters interact by verb class (which methods need confirm:YES and dry_run:false, and that dry_run defaults to preview). It does not add syntax guidance for path/query/body beyond what the schema states.

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?

States a specific verb+resource ('generic passthrough to any Action1 API path') and immediately distinguishes itself from the ~140 dedicated siblings by declaring it bypasses per-tool schemas. An agent can tell exactly what this tool is for without opening the schema.

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?

'use only when no dedicated tool exists' is an explicit exclusion rule that routes the agent to the sibling tools first. It also splits usage by method class (GET/HEAD free vs. mutating verbs gated), giving concrete conditions rather than vague intent.

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