clm_site_equipment_command_create_or_update_equipment

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

Beyond the sparse annotation (destructiveHint: false), the description discloses meaningful behavioral side effects: creating/recreating a calendar reservation object, conditionally publishing an availability-set command, and queuing a background command for zone attachment refresh. This gives the agent a strong sense of what invoking the tool will actually do.

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, dense sentence that front-loads the primary action and then conveys important side effects. It contains no filler, though the parenthetical side-effect chains make it somewhat heavy.

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 complex mutation command with a large undocumented parameter surface and only a destructiveHint annotation, the description covers the high-level flow but leaves critical gaps: no guidance on required fields, no identifier semantics, no explanation of bookable versus non-bookable behavior, and no clarification of update-versus-create selection logic.

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 description coverage is 0%, and the nested params object contains 30+ undocumented properties, yet the description names none of them. It does not explain which fields identify an existing record, which are needed for creation, or what concepts like BookableType, CapacitySchedule, or EquipmentPurposeLangKey mean.

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 a specific verb ('Creates... or updates...') and a clear resource ('site equipment master record'), and adds side-effect detail that distinguishes it from related equipment commands like upsert_unplanned_equipment or update_equipment_status. The create/update branches are explicit and unambiguous.

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 clearly implies when to use it: when creating a new site equipment master record or updating an existing one. However, it does not explicitly mention alternatives, exclusions, or conditions that should route an agent to a different tool such as upsert_unplanned_equipment or update_equipment_status.

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