unreal_functional_cancel

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

The annotations already indicate this is destructive and not read-only, so the description's extra note that it 'leaves the user's PIE session running' adds valuable nuance about what is and is not cleaned up. It does not contradict the annotations, and it helps prevent an agent from assuming the whole session is terminated.

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 two short sentences with no filler. The primary action is front-loaded, and the important side-effect note about the PIE session is placed clearly. Every sentence earns its place.

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 one-parameter destructive tool, annotations and the output schema cover safety and return values, and the PIE-session note is helpful. However, the description does not explain where job_id comes from, what qualifies as a 'bridge-owned test', or how this tool differs from other cancel tools, leaving an agent with meaningful gaps.

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 single parameter, job_id, has 0% schema description coverage and is not addressed in the description. The description's reference to 'this bridge-owned test' weakly implies job_id identifies such a test, but it never explicitly explains what job_id should be, where it comes from, or how it maps to the test being cleaned up.

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 states a concrete action ('Finish/clean up this bridge-owned test') and identifies the resource being acted on. It is clearly a cancellation/cleanup tool, but the terms 'bridge-owned test' and 'PIE session' are jargon that is not explained, and it does not explicitly differentiate it from sibling cancel tools like unreal_validation_cancel or unreal_performance_cancel.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'this bridge-owned test' implies it is for tests started by the bridge, but no conditions, prerequisites, or exclusions are provided, so an agent cannot confidently decide between this and related functional/validation/performance cancel tools.

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