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

Annotations only indicate readOnlyHint=false, so the description adds significant behavioral context: it requires a confirm parameter set to SEND_MAIL, imposes business permissions, and describes precondition checks. This goes beyond annotations.

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 the main action but contains redundant clarification about interchangeability. It could be more concise without losing essential preconditions.

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 complexity (7 parameters, no output schema, minimal annotations), the description is incomplete. It covers preconditions but not return values, error handling, or detailed parameter behaviors, leaving significant gaps for an effective call.

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 should compensate but only adds meaning for one parameter (confirm: must be set to SEND_MAIL). Other parameters like mailType, recipients, mailSubject remain unexplained, leaving the agent with insufficient guidance.

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 sends community mail to recipients (specific verb+resource). However, it confusingly claims 'business and community refer to the same thing and are interchangeable,' despite the existence of a sibling tool 'send_business_mail.' This undermines differentiation and creates ambiguity.

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 procedural guidelines: check business permissions, free businesses cannot use, call check_business_tool_access, show warnings, and never proceed when access is blocked. However, it does not compare this tool to alternatives like send_business_mail or send_magic_reach_message.

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