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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds constraints about FREE businesses and the need to show warnings, which goes beyond annotations. However, it does not detail all behavioral traits like idempotency or pagination.

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 efficient, packing important usage guidelines into a few sentences without fluff. It is front-loaded with the purpose and then provides sequential instructions. Minor redundancy in the first sentence ('Business and community refer to the same thing') but acceptable.

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 simple input schema (2 strings) and no output schema, the description adequately covers prerequisites and guardrails. It omits details about the response structure, but for a basic retrieval tool, the purpose is clear enough. An extra sentence on returned fields would improve completeness.

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 description coverage is 0%, and the description does not explain the two parameters (communityId and discountId) beyond their names. While the names are somewhat self-explanatory, the description should explicitly state what each parameter is or provide format constraints.

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 'Get details for one community discount.' It distinguishes from siblings like create_community_discount and get_business_discount, though the title mismatch ('Get Business Discount') could cause initial 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, avoid FREE businesses, call check_business_tool_access first, and handle grace-period warnings and resubscribe links. Also states never to proceed when access is blocked. This provides comprehensive when-to-use and when-not-to-use guidance.

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