execute_reduction

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

Annotations already flag destructive, open-world, non-idempotent behavior, so the description does not need to restate that. It adds the specific behavior of 'independently revalidate its candidate,' which is useful context, but it does not disclose what side effects occur, what 'lifecycle' entails, or what gets consumed or changed.

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 one tight, action-first sentence with no filler. It is efficient, but the terseness contributes to ambiguity around domain-specific terms like 'bound reducer lifecycle' and 'candidate,' so it is not a perfect balance of brevity and clarity.

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 destructive, open-world, non-idempotent tool, the description is too incomplete: it does not state prerequisites, what makes a reducer 'bound,' what a lifecycle execution actually does, or how this relates to plan_reduction/get_reduction. The presence of an output schema covers return values, but the surrounding execution context is missing.

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%, so the description is the only place to explain plan_id, yet it never mentions the parameter or how to obtain it. The phrase 'bound reducer' loosely hints at a prior plan object, but the relationship between plan_id and 'bound reducer lifecycle' is left implicit rather than stated.

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 names a specific action ('execute') and resource ('one bound reducer lifecycle') and adds a behavioral nuance ('independently revalidate its candidate') that goes beyond the bare tool name. However, it does not explicitly differentiate this from closely related siblings like plan_reduction or get_reduction, relying on the term 'bound reducer' to imply the distinction.

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 on when to invoke this tool versus alternatives such as plan_reduction, get_reduction, or list_artifact_reductions. The phrase 'bound reducer lifecycle' suggests a prior planning step, but no prerequisites, sequencing, or exclusion conditions are stated.

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