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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds important behavioral context such as permission requirements, free business restrictions, and grace-period warnings, which goes beyond what annotations provide.

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?

Description is well-structured with purpose first, then usage guidelines. Five sentences are appropriate and each sentence adds value, though the guidelines section is somewhat lengthy.

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?

While permissions and usage are covered, there is no information about what revenue summary data is returned (no output schema) or how to specify date range parameters. The tool has 4 parameters and no output schema, so the description should provide more context.

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% and the description does not explain any of the four parameters (communityId, startDate, endDate, duration). The agent has no information on how to use date range or duration 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?

Clearly states 'Get revenue summary data for a community' and clarifies that business and community are interchangeable. However, the sibling tool get_community_revenues exists, and no distinction is made, which could cause confusion.

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?

Explicitly instructs to check permissions using check_business_tool_access, notes that FREE businesses cannot use the tool, and mandates showing warnings and resubscribe links. Provides clear when-to-use and prerequisite guidelines.

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