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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds critical behavioral context: the tool is an existence check, and importantly, it has access restrictions based on business type (FREE businesses cannot use). No contradictions with 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 somewhat long (six sentences) but each sentence adds value: core purpose, terminology clarification, usage prerequisites, and enforcement rules. It is front-loaded with the main action. Minor redundancy could be trimmed but overall 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?

Given no output schema, the description does not state the return value format (e.g., boolean). It also does not cover the parameters, which are necessary for complete understanding. While the usage guidelines are thorough, the lack of parameter and return value information leaves the tool description incomplete for an AI agent to invoke correctly without additional schema parsing.

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%, meaning the description does not explain any of the four parameters (communityId, month, year, timezone). The description focuses solely on usage policy and completely neglects to describe what the parameters mean or how they constrain the query. This is a significant gap for a tool with multiple parameters.

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 checks the existence of a community monthly summary. It also clarifies the interchangeability of 'business' and 'community', which helps avoid confusion with similarly named sibling tools like check_business_summary_exists. However, it does not explicitly distinguish from other checking tools beyond that.

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 extensive usage guidelines: it specifies prerequisites (check business permissions, call check_business_tool_access), conditions for use (FREE businesses cannot use), and required user interactions (show grace-period warning, resubscribe link, never proceed when blocked). This fully informs when and how to use the tool.

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