clm_site_equipment_command_create_equipment_booking_from_mobile

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

The description discloses more than the annotations alone: it notes that the tool queues a background command that finalizes the booking via timeline creation and approval notifications. This gives the agent a meaningful picture of side effects, though it does not cover failure behavior or idempotency.

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 core action and then adds relevant detail. It is not overly verbose, though the long parenthetical list makes it slightly harder to parse quickly.

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 16-field creation tool with zero parameter descriptions, the description gives a solid high-level overview and a useful lifecycle explanation, but it is not complete enough to fully guide correct invocation. The agent still must infer the meaning of many parameters and the exact relationship to sibling save/update commands.

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%, so the description must compensate, but it only provides broad groupings like 'booking date/slots, transport info, and other info'. It does not explain ambiguous fields such as ItemId, EquipmentId, Building, Floor, RecipientClmTeamId, or TimeZoneOffset, leaving significant semantic gaps for the agent.

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 tool creates a new site equipment booking from mobile in a single call, explicitly distinguishing it from the sibling update_equipment_booking_from_mobile and the partial save_* commands. It names the resource, the action, and the overall scope, so an agent can immediately understand what this 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 phrase 'submitted from the mobile app in a single call' gives clear context for when this tool is appropriate, especially against sibling partial-save commands. However, it does not explicitly name alternatives or state when not to use this tool, so some routing inference is still required.

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