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

Beyond annotations (readOnlyHint=true), the description adds critical behavioral context: permission requirements, business tier restrictions, prerequisite call to check_business_tool_access, and user-facing warning/link obligations. This fully discloses the operational constraints and side effects.

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 front-loaded with purpose and then provides procedural instructions. Every sentence adds value, though it could be slightly more concise by separating usage guidelines from parameter explanations.

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 lacks information about the return value or output format, which is critical for a read-only tool with no output schema. It also does not explain how the four parameters interact, leaving gaps in the agent's understanding of context and results.

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 only hints at 'mailType' from the purpose statement. It does not explain the 'default', 'communityId', or 'mailCourseOffer' parameters, leaving the agent blind to their meanings and usage.

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 tool retrieves community mail content for a mail type, with a note that 'business' and 'community' are interchangeable. However, it does not distinguish between this tool and the sibling 'get_community_mail', which may cause confusion as they appear to serve the same purpose.

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, step-by-step usage guidance: check permissions, call check_business_tool_access first, show grace-period warnings and resubscribe links, and never proceed when access is blocked. This clearly instructs the agent on when and how to use the tool, including exclusions (FREE businesses).

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