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

The description adds context beyond annotations (readOnlyHint=false) by explaining that the tool can create state and that access restrictions apply. It does not mention rate limits or idempotency, but the prerequisites and restrictions are well covered.

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 front-loaded with purpose and then provides clear usage instructions. It is slightly verbose but every sentence adds value, though it could be more concise by integrating the interchangeable statement.

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 tool is simple with one parameter and no output schema. The description covers purpose and usage well but omits what the tool returns (the referral code) and does not explain the parameter. This leaves the agent guessing about output and parameter binding.

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 only parameter 'communityId' has no description in the schema (0% coverage) and the description does not explain its meaning or format. Since 'business' and 'community' are said to be interchangeable, it is unclear if communityId refers to a business ID or something else.

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 or creates a referral code for a managed community, and clarifies that business and community are interchangeable. However, it does not differentiate from the sibling tool 'retrieve_or_create_community_referral_code', which may cause confusion since both exist.

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 business permissions and call 'check_business_tool_access' before using, details that FREE businesses cannot use it, and specifies to show grace-period warnings and resubscribe links. This provides clear 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.