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

Description adds context beyond annotations: requires permission checks, FREE businesses cannot use, and a pre-check tool must be called. It does not contradict annotations (readOnlyHint=false, destructiveHint=false). While it doesn't describe all behavioral traits (e.g., side effects, rate limits), it provides useful operational context.

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 dense and includes critical information in a logical order. Each sentence serves a purpose. It could be slightly more concise by merging some sentences, but overall efficient and well-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?

Covers purpose, prerequisites, permission checks, and restrictions. However, it lacks details on return value (no output schema) and does not explain all parameters (e.g., content object structure, mailCourseOffer). For a tool with 6 parameters and nested objects, more completeness is needed.

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 coverage is 0%, so description must compensate. It mentions 'content' and 'subject' will be updated, adding meaning beyond schema. However, it does not explain 'mailType', 'isEnabled', or 'mailCourseOffer', leaving gaps. Baseline for 0 params is 4, but partial explanation warrants a 3.

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 updates community mail content and subject, and clarifies that 'business' and 'community' are interchangeable. This distinguishes it from sibling tools like 'send_community_mail' (sends mail) and 'update_business_mail' (similar but for business entities).

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?

Explicit guidelines: before using, check business permissions, call 'check_business_tool_access', show grace-period warning and verified resubscribe link, and never proceed when access is blocked. This tells agents exactly when and when not to use the tool, including prerequisites and alternative steps.

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