Execute Code Task Locally

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

Annotations already indicate this is a destructive operation, but the description adds no behavioral detail about what gets modified, whether rollback is possible, or what side effects may occur. The contrast with the compact version implies missing safety features, but this is not explicitly disclosed.

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 extremely compact with only two sentences and no filler. The purpose is front-loaded and the alternative is named immediately, but the first sentence is cryptic enough to reduce 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 tool with 10 parameters and no output schema, this description is drastically incomplete. It omits return behavior, file modification semantics, retry/rollback behavior, validation execution details, and any usage conditions. The agent cannot safely invoke this tool based on the description alone.

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% and the description adds no meaning for any of the 10 parameters. Critical parameters like editableFiles, rollbackOnFailure, validation, constraints, and maxAttempts are entirely unexplained, leaving the agent to guess their semantics.

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 title and description make clear the tool executes code tasks locally, and the phrase 'Compatibility full-result executor' distinguishes it from its compact sibling at a high level. However, 'compatibility full-result executor' is jargon and does not precisely explain what the tool does or what 'full-result' means.

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 explicitly says to prefer execute_local_code_task_compact and gives concrete reasons: routing preflight, adaptive fast-to-strong retry, and supervised-sensitive review enforcement. It does not, however, state the specific conditions under which this compatibility version should be used instead.

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