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

Annotations indicate it's not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds behavioral context about permission checks and restrictions (FREE businesses blocked), which goes beyond annotations. It does not contradict any annotation.

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 5 sentences, front-loading the action and then providing essential usage guidelines. It is concise with no redundancies, though it could be slightly more efficient by grouping related conditions.

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 has no output schema and is a mutation. While preconditions are well-covered, the description omits what happens after execution (e.g., success response, side effects) and does not detail the structure of tieredPrices. For a 2-parameter tool with an array of objects, this is incomplete.

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?

Input schema has 2 required parameters (communityId, tieredPrices) with zero description coverage in schema. The description fails to explain what communityId represents or the expected structure of tieredPrices array (e.g., fields, format). This is a significant gap for a tool with undocumented 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 it updates membership tiers and prices for a managed community, and clarifies that 'business' and 'community' are interchangeable. However, it does not explicitly distinguish from sibling tools like 'update_business_tiered_prices' or 'calculate_community_price', though the context of community is clear.

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, actionable instructions: check business permissions, note that FREE businesses cannot use the tool, call 'check_business_tool_access' before collecting inputs, and handle grace-period warnings and resubscribe links. It also states never proceed when access is blocked, giving clear when-to-use guidance.

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