shelf_checkin_booking

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation. The description adds the meaningful scope detail that ALL assets in the booking are checked in at once, but says nothing about required permissions, whether the action is reversible, or what happens with already-returned assets.

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?

A single short sentence, front-loaded with verb and resource, with zero filler. Every token contributes to selection or scoping.

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 state-changing booking operation with no output schema, the definition covers the core action but omits the preconditions and outcome semantics an agent needs (must the booking be checked out? what state results?). Annotations carry the safety profile, so the gap is moderate rather than severe.

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 67%, with orgId and timeZone documented but bookingId bare. The '(all assets)' note slightly clarifies the semantics of the booking reference, but the description adds no format, constraint, or default information beyond the schema.

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?

Specific verb ('check in') plus resource ('booking'), with scope qualifiers ('ongoing/overdue', 'all assets'). It is distinguishable from the inverse sibling shelf_checkout_booking, though it never names or contrasts with any sibling explicitly.

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 'ongoing/overdue booking' implies the eligibility condition for use, but there is no explicit when-to-use guidance, no prerequisites (e.g. booking must already be checked out), and no named alternative for the reverse operation.

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