List bookings needing attention

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

Annotations already cover readOnly, idempotent and non-destructive, so the bar is lower. The description still adds real operational context: required scopes (bookings:read, luca:read), full_content data sensitivity, and that no idempotency key is needed. It does not disclose pagination, result volume, or whether the disagreements are pre-filtered by severity.

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 distinguishing definition is front-loaded in one sentence, followed by a compact metadata block (endpoint, scopes, idempotency, workspace override). Most lines earn their place, though 'Does not require idempotency' is partly redundant against the idempotentHint annotation.

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?

With an output schema present, return values need not be described, and the description supplies the endpoint, auth scopes, sensitivity level and workspace override behavior. What remains thin is the relationship to the resolution/retry siblings and any hint about how many items or how often to re-check.

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 coverage is 100%, so both optional parameters are already documented, giving a baseline of 3. The description's 'Use workspaceId or workspaceSlug to override the default workspace configured by environment' adds the useful fact that a default exists and these are overrides, but nothing about precedence when both are supplied.

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 first sentence gives a precise verb+resource and a genuinely distinguishing scope: bookings where Luca's record and the provider's disagree and a human must decide. That clearly separates it from luca_bookings_list and luca_bookings_needs_outcome. It stops short of naming the sibling it feeds into (luca_bookings_lifecycle_resolution), so it is not a 5.

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?

Usage is only implied: the agent can infer this is the read step before calling luca_bookings_lifecycle_resolution, but the description never says when to use this versus that resolution tool, nor whether it should be polled or is event-driven. No explicit when/when-not guidance is present.

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