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

The description adds behavioral context beyond annotations: permission requirements, free business restriction, required pre-check via another tool, and handling of warnings. Annotations only declare readOnlyHint=true and destructiveHint=false, which this description complements without contradiction.

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 well-structured: it opens with the purpose, then provides step-by-step usage instructions. While every sentence adds value, it could be slightly more concise by integrating the instructions more tightly. Still, it is efficient and front-loaded.

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?

Given the tool has 5 parameters, no output schema, and minimal annotations, the description covers the essential usage context (permissions, pre-checks) but lacks parameter details. The schema enums mitigate some ambiguity. The description is fairly complete for an export tool, though it doesn't describe the CSV output format beyond the title.

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%, yet the description does not explain any of the 5 parameters (communityId, sessionId, type, order, search). While the enums for type and order are somewhat self-explanatory, the description fails to add meaning beyond the schema. For a tool with low coverage, this is a significant gap.

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 action ('Export'), the resource ('one-on-one session bookings'), the format ('CSV text'), and the context ('for a managed session'). It distinguishes from sibling export tools like 'export_business_members' or 'export_lead_form_applicants_csv' by specifying session bookings.

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 explicit when-to-use and when-not-to-use guidance: check business permissions, FREE businesses cannot use, call 'check_business_tool_access' first, show grace-period warnings and resubscribe link, and never proceed when access is blocked. This is comprehensive and actionable.

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