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

With no annotations, the description fully discloses important behaviors: atomic application of approval, rejection reason requirement (min 10 chars), idempotency with conflict return, and emission of session lifecycle events. This exceeds typical transparency for mutation tools.

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 description is three sentences, each adding substantive value: purpose, outcome details, and behavioral guarantees. No redundant phrasing, and the information is front-loaded with the core action in the first sentence.

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 mutation tool with no annotations or output schema, the description covers purpose, side effects, idempotency, and validation. It doesn't describe the success response format, but this may be acceptable given the output is likely a standard status object. Overall, it's adequate for an agent to invoke correctly.

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?

The description adds essential semantics for outcome (approved/rejected meanings) and reveals a minLength constraint on reason not present in the schema. However, requestId, orgSlug, and apiKey are left to inference, which is acceptable given their common usage but not fully compensated for with 0% schema coverage.

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 clearly states the tool's purpose: 'Approve or reject a pending reschedule request (SessionRequest) that a client proposed from the portal'. It uses specific verbs (approve/reject) and identifies the resource (pending reschedule request), distinguishing it from sibling tools like portal_propose_reschedule and booking_reschedule.

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 provides strong contextual guidance by indicating this is for resolving client-proposed requests, including atomic approval and rejection criteria. It doesn't explicitly list alternatives, but the phrase 'closes the bilateral coordination loop' implies the appropriate workflow stage. The idempotency note also clarifies what happens if used incorrectly.

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