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

Annotations already declare readOnlyHint=true, and the description adds context about required permission checks and access restrictions. No contradiction; it provides useful behavioral context beyond the 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 five sentences, each adding necessary information. It is front-loaded with the purpose. While concise, it could be slightly tighter by combining some steps.

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?

The description covers prerequisites and access restrictions, which is important for a simple get tool. However, it lacks parameter descriptions and does not specify the return format (no output schema), leaving gaps in 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?

The input schema has 0% description coverage, and the description does not explain the two required parameters (discountId, communityId) beyond implying their purpose from the context. The agent is left to infer parameter semantics.

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' and clarifies that 'business and community refer to the same thing'. This provides a specific verb and resource, though the interchangeable naming could cause confusion with the sibling tool get_community_discount.

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 states when to use (e.g., after checking permissions and calling check_business_tool_access), when not to use (FREE businesses cannot use this tool), and provides explicit steps including showing grace-period warnings and verified resubscribe links.

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