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

Annotations carry only destructiveHint=true, so the description does the heavy lifting and delivers: it declares a write, that charges accrue per the resource rate by default, that the member is notified unless silenced, and that the flex.space.bookings.create scope is required. It omits conflict/double-booking handling and rate limits, so not a full 5.

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?

Three tight sentences with the operation type front-loaded and no filler; each clause conveys either scope, behavior, or auth requirement.

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 13-parameter mutation with no output schema and only a destructiveHint annotation, the description covers the essential behavior an agent needs: write semantics, default charging, notification, and required scope. Return shape is excusably absent given no output schema, though conflict/failure behavior is unaddressed.

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 100%, so every one of the 13 parameters is already documented in the schema, making 3 the baseline. The description clarifies the default charging model and reiterates the is_free/is_tentative/is_silent interplay, but adds little semantics beyond what the individual parameter descriptions already state.

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?

Opens with a specific verb+resource ('WRITE. Book a resource (e.g. a meeting room) for a member and/or company'), immediately distinguishing it from read-side siblings like officernd_get_booking and officernd_list_bookings. The scope tag and REST endpoint (POST /bookings) pin down exactly which operation this is.

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 gives conditional context ('unless is_free or is_tentative is set...', 'unless is_silent') which implies when certain behaviors apply, but never states when to choose this tool over siblings or any prerequisites beyond the scope. Usage is inferred rather than directed.

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