Propose Patch

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

The description does not disclose any behavioral traits. It mentions a fix but not the tool's action (creating a patch). Annotations exist but are insufficiently supplemented. No contradiction with annotations.

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 very short but fails to communicate tool purpose. It is under-specified rather than concise; every sentence should add value, but this one does not.

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?

Given no output schema, no parameter descriptions, and a non-descriptive annotation, the description is completely inadequate for a tool with two required parameters and related siblings.

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 input schema has two required parameters (edits, contextId) with no descriptions. The description adds no information about their meaning or purpose, and schema coverage is 0%.

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 'FIXED: patchId linked to validate/apply via randomUUID' is a changelog note, not a statement of tool purpose. It does not specify what the tool does, such as proposing a patch, which is implied by its name and siblings.

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?

No usage guidance is provided. The description offers no context on when to use this tool versus siblings like patch.validate, patch.apply, or patchset.propose.

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