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

Annotations indicate read-only and non-destructive behavior. The description adds valuable context about free business restrictions, required permission checks, and warning handling, which are not conveyed by annotations alone.

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 concise given the amount of usage guidance provided. It could be slightly tighter by removing the redundant 'Business and community refer to the same thing' clarification, but it remains well-structured and front-loaded.

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?

Despite strong usage guidelines, the description lacks details on parameter semantics and return values. Without an output schema or parameter explanations, the agent cannot fully understand how to invoke the tool or interpret 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 should explain parameter usage. It mentions 'monthly summary' but does not describe the 'date' parameter's format, purpose, or that it is optional. The 'communityId' parameter is also not explained, leaving significant ambiguity.

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 it retrieves a monthly summary for a managed community. However, it does not clarify the role of the 'date' parameter or whether the summary is fixed to a specific month, leaving some ambiguity about the tool's exact scope.

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 preconditions: check business permissions, call check_business_tool_access, show grace-period warnings, and never proceed when access is blocked. This offers clear when-to-use and when-not-to-use guidance, surpassing typical descriptions.

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