clm_site_equipment_command_delete_equipment

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

The description goes well beyond the destructiveHint annotation by disclosing that deletion is permanent, that background commands are queued, and that behavior is conditional for bookable equipment. This gives the agent a strong understanding of side effects and irreversibility.

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 a single front-loaded sentence with no filler. It states the core action first, then adds valuable detail about side effects and conditional behavior. Every clause earns its place.

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 destructive command with an output schema, the description is complete: it states the target resource, permanence, queued background actions, and condition for bookable equipment. No critical behavioral information is missing.

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 description coverage is 0%, but EquipmentId is self-descriptive and the deletion action implies it identifies the target site equipment record. However, the description does not explicitly explain how to use EquipmentId or address the parameter's null default, leaving some ambiguity.

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 uses a specific verb and resource: 'Permanently deletes a site equipment record.' It also uniquely describes cascading behavior by queuing background commands to remove zone attachments and booking prerequisites, which distinguishes it from sibling delete/discard tools. This is clear and specific enough for an agent to understand what the tool does.

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 provides clear context for when to use the tool: when a site equipment record needs to be permanently deleted along with its associated cleanup. It does not explicitly name alternatives or exclusions, but the resource scope is clear enough that an agent can infer the appropriate usage context.

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