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

Annotations already mark destructiveHint: true, but the description adds critical context: the confirm parameter must be exactly 'CANCEL', business permissions are required, and FREE businesses are excluded. It also mentions showing grace-period warnings and verifying resubscribe link. These go beyond annotations to fully disclose behavior and safety steps.

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 somewhat verbose but each sentence adds value. It is front-loaded with the purpose and confirm requirement. Could be slightly more concise by combining sentences, but it is well-structured and easy to follow.

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 usage guidelines and behavioral context well, but lacks details on return values or side effects (e.g., what happens after cancellation, whether refunds are processed). Given no output schema, this is a gap. Also, parameter details are missing. For a complex 7-parameter tool, more completeness is expected.

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. However, it only explains the confirm parameter ('set to CANCEL'). The other six parameters (bookingId, sessionId, communityId, requestRefund, transactionId, reasonForRefund) are left entirely to name inference. This is insufficient for an agent to understand their purpose or constraints.

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?

Clearly states it cancels a one-on-one session booking. Specific verb+resource. Distinguishes from siblings like delete_session (which deletes the session itself) and update_session (which modifies bookings). The description also specifies the required confirm parameter value, adding precision.

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: requires confirm set to CANCEL, mandates checking business permissions via check_business_tool_access, warns that FREE businesses cannot use regardless of features, instructs showing grace-period warning and resubscribe link, and forbids proceeding when access is blocked. This is comprehensive and prevents misuse.

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