invert

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

The annotations already flag destructive behavior (destructiveHint: true). The description adds the useful behavioral note that a checkpoint happens first, which complements the destructive annotation rather than contradicting it. It does not go into further depth about in-place modification, but the simple nature of 'invert' makes that less critical.

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 concise, with two short sentences that each carry useful information. There is no filler or redundancy, and the core 'invert a view' purpose is front-loaded.

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 single-resource operation, the definition is nearly complete: purpose, target use, destructive safety, and a checkpoint instruction are all present. The main gap is that 'id' is not described, but its role is inferable from 'view' and the required parameter is clearly named in the schema.

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 description adds no real meaning beyond the input schema. 'Checkpoints first' merely echoes the checkpoint parameter's existing schema description, and the required 'id' parameter is left completely undescribed in both the schema and the description. With 50% schema coverage, the description should compensate but does not.

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?

'Invert a view (useful on masks)' states a specific verb and resource, and the parenthetical gives a concrete use case. It is not tautological and is distinct enough from the many sibling image-processing tools, though it does not explicitly name a sibling alternative.

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 indicates which target it is useful for ('masks') and provides the operational guidance 'Checkpoints first,' which is especially relevant because the annotations mark this as destructive. It lacks an explicit when-not-to-use or comparison to alternatives, so it stops short of a 5.

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