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

With no annotations supplied, the description carries the full burden and does add real behavioral context: confirmation does not equal payment, and the backing service re-validates organization permissions and schedule conflicts. That tells the agent that a successful confirm is not final and may fail on backend checks. It stops short of describing what a stale preview returns or how errors surface.

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?

Extremely front-loaded and free of filler; the scope rule comes first and the safety caveat last. The telegraphic '+' notation and compressed clauses cost some readability, but no sentence is wasted.

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 an 11-parameter, dual-mode tool with no annotations and no output schema, the description leaves major gaps: pagination (limit/cursor), the consent boolean, how previewHash binds a preview to a decision, and what a list response contains are all undocumented. It answers the workflow question but not enough for an agent to invoke the tool correctly end-to-end.

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% across 11 parameters, so the description must compensate, and it only covers box, action, decision and the preview precondition. Seven parameters — note, limit, cursor, consent, bookingId, previewHash, organizationId — get no semantic explanation at all, notably consent (const true) and previewHash (64-char hash) whose relationship to preview is left implicit.

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 maps the tool's modes (list+outgoing vs incoming, respond+confirm/decline) but never states plainly that this tool lists and answers ecosystem venue booking requests — the resource is only identifiable from the tool name and title. An agent can infer the purpose from the mode shorthand plus the sibling get_ecosystem_venue_availability, but it is inference rather than a stated verb+resource.

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?

It explicitly states the condition that selects each mode: outgoing for one's own bookings, incoming only for venue staff, and it imposes a mandatory workflow (preview the current request before confirming/declining). What it lacks is tool-level routing — it never says when to use this versus get_ecosystem_venue_availability or reserve_activity_registration.

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