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

Goes well beyond the annotations: it discloses the side effect (booking leaves the unassigned folder), the pairing permission prerequisite, the default confirmation prompt (and that it can be disabled), that the call reaches other people, and the API-key access requirement. This is the kind of write/auth/confirmation context annotations alone cannot convey.

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?

Front-loaded with the core action and generally efficient, but the first two sentences restate the same assignment action, which is mild redundancy in an otherwise tight block.

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 no output schema, the description carries the return-value burden adequately by explaining the observable consequence (removal from the unassigned folder) and covers mutation effect, permissions, confirmation, and auth. Nothing needed to call it correctly is missing.

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% and both parameters are already described (booking_id from list_bookings; provider_ids as one provider/team or several to pair). The description reinforces the pairing semantics but adds little the schema does not already say, so baseline 3 applies.

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?

States a specific verb (assign) and resource (provider/team to a booking), plus the pairing variant, in the first sentence. An agent can distinguish this from siblings like bookingkoala_list_providers or bookingkoala_get_booking without opening any schema.

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?

Explains the two usage modes (single assignment vs. multiple provider_ids for pairing) and the precondition that pairing requires scheduling permission and provider-level enablement. It does not explicitly name an alternative tool for the single-provider case, but the conditions that select each behavior are clear.

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