delete_gear

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

Annotations only declare destructiveHint/readOnlyHint/openWorldHint generically; the description goes further by disclosing exactly what is destroyed (the gear AND its activity history), the return behavior (resolves null on 204), and the UUID hyphenation gotcha that causes 404s. This is substantial behavioral context beyond the structured fields.

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 endpoint method and the destructive warning are front-loaded well, but the duplicated 'IRREVERSIBLE:' fragment is a clear typo/formatting artifact that wastes space. Overall the passage is reasonably dense but not clean.

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 single-param destructive tool with no output schema, the definition covers the return value (null/204), the destruction scope, and the UUID format trap. It is nearly complete; the only omission is any note about permissions/auth failure modes, which is minor.

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 coverage is 0%, so the description must carry the parameter burden, and it does: it explains the required hyphenated UUID form, that `getGear` returns the bare 32-char form, and that the method auto-re-inserts hyphens so either form works. That meaningfully exceeds the bare `gearUUID: string` schema, though it doesn't document the parameter name explicitly.

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 names the exact endpoint (`DELETE /gear-service/gear/v2/{gearUUID}`) and the resource it operates on, so the verb+resource are unambiguous. It does not explicitly contrast itself with the sibling `remove_gear_from_activity`, but the scope (deleting the gear itself) is clear enough to distinguish it from unlinking a gear from an activity.

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?

It gives a strong operational directive ('confirm with the user before calling') which is genuine when-to-invoke guidance for a destructive op. However, it offers no comparison to alternatives like `remove_gear_from_activity` or `create_gear`, and no prerequisites beyond the confirmation warning.

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