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

Annotations already indicate readOnlyHint=true, so the read-only nature is known. The description adds important behavioral context about permission checks and business restrictions, which are not in annotations. No contradictions.

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 one paragraph that efficiently conveys purpose then usage guidelines. It front-loads the core action and avoids unnecessary details, though it could be slightly more structured.

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 tool has 5 required parameters, no output schema, and low schema coverage. The description provides essential usage context and some parameter hints, but lacks details on output format, pagination, or error handling. Adequate but not fully complete.

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?

With 0% schema description coverage, the description partially compensates by explaining 'date range' (likely rangeStart/rangeEnd) and 'attendee timezone' (timezone), but does not explicitly map to parameters or clarify communityId, sessionId, or date/time formats. Minimal addition beyond schema.

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 verb 'List' and resource 'available one-on-one session slots' with specific filtering by date range and timezone. It distinguishes from siblings like list_session_bookings and get_session by specifying the slot focus and required parameters.

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?

Provides explicit guidance: check business permissions, FREE businesses cannot use it, call check_business_tool_access before inputs, handle grace-period warnings and resubscribe links, and never proceed if access is blocked. This clearly tells when and how to use the tool versus alternatives.

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