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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. Beyond that, the description adds important behavioral constraints: permission gating via check_business_tool_access, a FREE-plan hard block, and requirements to show grace-period warnings and a verified resubscribe link before continuing. This is substantial context an agent needs to avoid unauthorized use.

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 purpose is front-loaded in the first sentence, and the permission requirements follow in a logical order. There is some repetition around checking access before collecting inputs, but the description remains compact and each sentence contributes to safe usage.

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?

The description covers the core purpose and critical permission gating, but with five parameters, 0% schema description coverage, and no output schema, it should explain what the parameters mean and what the CSV export contains. An agent can infer some intent from parameter names and enums, but the definition stops short of being fully self-contained.

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%, and the description does not explain any of the five parameters (communityId, sessionId, type, order, search). 'For a managed session' only loosely hints at sessionId, leaving the meanings of type, order, and search entirely undocumented in both the schema and the description.

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 states a specific verb and resource: 'Export one-on-one session bookings as CSV text for a managed session.' It identifies the output format (CSV text) and the scope (one-on-one session bookings for a managed session), which separates it from sibling tools like list_session_bookings or export_business_members.

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 gives explicit preconditions: check business permissions first, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. It also states a hard exclusion: FREE businesses cannot use this tool regardless of individual feature rows. These are concrete when-to-use and when-not-to-use rules.

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