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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds important behavioral context: FREE businesses are blocked, access must be verified, and a grace-period warning/resubscribe link must be shown. This goes beyond the annotations without contradicting them.

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, relatively concise. It front-loads the purpose and follows with usage conditions. The sentence 'Business and community refer to the same thing and are interchangeable' could be shortened, but overall it is efficient.

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?

For a 3-parameter tool with no output schema, the description covers the action and access prerequisites but omits parameter details and return values. It provides adequate context for a write tool but leaves gaps in parameter usage.

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 3 parameters with no descriptions (0% coverage). The description only mentions 'permissions' in passing and does not explain communityId, membershipId, or the permissions object structure. No additional meaning is provided beyond the schema.

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 states 'Update permissions for a community manager membership' which is a clear verb+resource, but the title says 'Update Business Manager Config' and the description claims business and community are interchangeable, causing confusion. The purpose is somewhat vague due to this inconsistency.

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 states when to use the tool: check business permissions, call check_business_tool_access before collecting inputs, show grace-period warning and verified resubscribe link, and never proceed when access is blocked. It also notes FREE businesses cannot use it. This provides clear context, though no explicit exclusions of alternatives.

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