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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that FREE businesses cannot use the tool and involves calculating totals/fees/pass-on handling. It does not contradict annotations, but lacks details on side effects or response behavior 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?

The description is brief at five sentences, front-loading the purpose and following with prerequisites. Every sentence adds value, and the structure is logical.

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?

With no output schema and five parameters lacking schema descriptions, the description should cover return values and full parameter semantics. It does not explain what the tool returns or handle errors, leaving significant gaps for an agent to invoke it correctly.

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%, requiring the description to compensate. The description vaguely mentions communityId, itemPrice, shippingFee, and isPassOn via 'fees' and 'pass-on handling', but does not explain entityType or provide clear definitions for each parameter. This is insufficient for understanding all five 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?

The description clearly states the tool calculates community price totals, fees, and pass-on handling. It also clarifies that business and community are interchangeable. However, it does not differentiate from the sibling tool 'calculate_community_price', which likely performs a similar function.

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 explicitly provides prerequisites: check business permissions, note that FREE businesses cannot use it, call check_business_tool_access before collecting inputs, and show grace-period warnings. It also specifies when not to proceed (access blocked). This offers clear guidance, including alternative steps.

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