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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: env var and auth header values are masked in the returned request preview, fieldOverrides map to AI-input values keyed by variable key, and remote side effects are possible. It doesn't cover return format details, but the added masking and request-assembly behavior is substantive.

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 core action and safety warning are front-loaded, and the sentence about request assembly packs a lot of useful detail without much waste. Slightly dense but well-structured.

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?

There is no output schema, so the description must carry the behavioral burden, which it largely does for the request mechanism and masking. However, for a destructive, open-world tool with zero schema coverage and a nested fieldOverrides object, the missing documentation of timeoutMs and bodyOverride leaves material gaps an agent needs to call it correctly.

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 0% across four parameters, so the schema provides no guidance. The description compensates for fieldOverrides (keyed by variable key, used as AI-input values) and explains toolId implicitly, but leaves timeoutMs and bodyOverride completely undocumented, leaving half the parameters ambiguous.

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 and resource ("Fire a real HTTP request for a saved tool") and immediately distinguishes itself via "bypassing the LLM", which contrasts with the sibling test_agent_tool. An agent can tell what this does 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?

The description explains the mechanism and warns "use carefully" with side effects, but it never explicitly says when to pick this over test_agent_tool or test_agent_tool_request alternatives. The usage context (tools with httpRequest.enabled, legacy serverUrl tools) is implied rather than stated as selection criteria.

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