remove_shape

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

With no annotations, the minimal description fails to disclose side effects (e.g., irreversibility, dependency on existence, undo behavior) beyond the basic destructive action.

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 single-sentence description is concise and front-loaded with the key action, though it could be slightly more structured to include essential context.

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 the tool's simplicity and no output schema, the description is minimally adequate for a straightforward deletion, but it lacks context about prerequisites, irreversibility, or related operations.

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 shape_id parameter is not described; with 0% schema coverage, the agent must infer its purpose from the tool name alone, lacking guidance on how to obtain a valid ID.

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 clearly states the action (remove) and the resource (a shape from the board), directly distinguishing it from sibling tools like add_shape or move_shape.

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 guidance is provided on when to use this tool versus alternatives like remove_track or remove_footprint, nor any prerequisites such as selecting or obtaining a shape_id.

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