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

With no annotations, the description carries the full burden. It discloses that the operation is read-only, lists what is returned (proposed slot, current session state, proposer), and mentions cursor pagination. It does not cover auth/rate limits, but the key behavioral traits are conveyed.

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 compact yet dense; every clause adds value. The first sentence is front-loaded with the core purpose, and subsequent sentences efficiently cover filters, return data, pagination, optional flag, read-only nature, and alternate action tool without redundancy.

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 list tool with 8 parameters and no output schema or annotations, the description is largely complete: it covers purpose, filters, return contents, pagination, and related tool. Minor gaps include explicit mention of the limit parameter and required orgSlug, but these are not critical for invocation.

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%, so the description must compensate. It adds meaning by documenting status values and default (pending|all|resolved), sessionId/clientId filters, includePendingCount purpose, and pagination. It omits explicit details for limit, apiKey, and orgSlug, but orgSlug is implied by 'organization' and apiKey is likely authentication.

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 uses a specific verb 'List' and identifies the resource 'reschedule requests (SessionRequest) of an organization', clearly distinguishing this from sibling tools like booking_resolve_request (action) and booking_list (general bookings). The mention of the 'org side of the bilateral coordination loop' adds context that separates it from client-side portal tools.

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 clearly states this is for the organization side of reschedule requests and explicitly recommends 'Use booking_resolve_request to approve or reject one', providing an alternative. Filtering options and default status are also specified, giving the agent clear when-to-use guidance.

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