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

The annotations indicate readOnlyHint=true and destructiveHint=false, which the description supports by stating it lists transactions. The description goes beyond annotations by specifying permission requirements and free-tier restrictions, adding valuable behavioral 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 concise, with a clear first sentence stating purpose followed by essential usage instructions. No extraneous information; every sentence adds value.

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 of 22 parameters and no output schema, the description fails to provide essential context. It does not explain parameter purpose, filtering capabilities, or return format, making it difficult for an agent to invoke the tool correctly without additional knowledge.

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?

The schema has 22 parameters with 0% description coverage, yet the description provides no information about any parameter's meaning or usage. The agent receives no help understanding the parameters beyond their names and types. This is a critical gap.

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 lists revenue transactions for a community managed by the authenticated user. It clarifies that 'business' and 'community' are interchangeable. However, it does not distinguish from the sibling tool 'list_community_transactions', which likely has the same purpose, leaving room for 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 usage guidance: check business permissions, note that FREE businesses cannot use this tool, call check_business_tool_access before collecting inputs, show grace-period warnings and resubscribe links, and never proceed when access is blocked. This is highly prescriptive and helps the agent decide when 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.