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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial operational behavior beyond them: result chaining via the `bucket` field, permission checks, FREE-tier restriction, required preflight access call, grace-period warning with verified resubscribe link, and a hard stop when access is blocked. This is a rich set of behavioral details.

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 the core purpose, followed by high-value chaining and permission instructions. Every sentence earns its place, with no redundant or filler content.

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?

Given there is no output schema, the description partially covers return values through the chaining note (`bucket`, `name`, `displayName`) and thoroughly covers access prerequisites. However, it omits the behavior and purpose of `filters` and `searchString`, and does not describe the overall result shape or pagination. Useful but incomplete for a 3-parameter tool.

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%, and the description does not explain the optional `filters` or `searchString` parameters or their expected formats. It implicitly identifies `communityId` via 'managed community' and mentions output fields `bucket`, `name`, and `displayName`, but leaves most parameters semantically undocumented.

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 opens with a specific verb and resource: 'List Magic Reach recipient buckets for a managed community,' which clearly distinguishes it from singular get_magic_reach_bucket and related list/search sibling tools. The additional chaining note further clarifies the tool's role in the Magic Reach workflow.

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?

Provides strong when-not guidance: FREE businesses cannot use the tool, and it mandates calling check_business_tool_access before collecting inputs, showing grace-period warnings, and stopping when access is blocked. It does not explicitly name alternative bucket-listing or recipient-listing tools for comparison, but the context is clear.

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