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

Annotations already supply destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description nonetheless adds real value by emphasizing permanence ('for good') and by contrasting with the reversible path. It leaves unstated whether auth/ownership is required or what happens when the id does not resolve.

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?

Two tight sentences: the destructive action first, then the routing alternative. No filler, and the most important constraint 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 two-param mutation with a destructive annotation and no output schema, the description covers the key agent question (delete vs. disable). The residual gap is the undocumented image_id, which the agent must infer from having listed the boat's images.

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 schema documents only 'id' (via list_boats) and leaves 'image_id' completely bare, and the description adds no parameter meaning at all — no format for image_id, no relation to the boat's cover image. At 50% schema coverage the description is expected to compensate, and it 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?

States a specific verb (delete) and narrowed resource (one photo of the boat), with an explicit scope of exactly one image. It also names the sibling tool it is not, so an agent can distinguish it from update_boat_images without opening either schema.

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?

Gives an explicit when-to-use versus alternative: destroy the photo with this tool, or remove it from the listing non-destructively with update_boat_images + disable_id. The decision criterion is fully spelled out, including the exact parameter of the alternative.

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