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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value by disclosing the return fields (id, name) and the backing GraphQL field ('passes'), which helps an agent connect the tool to the underlying API and anticipate output. It does not state whether the list is paginated or complete, but for a zero-parameter read this is strong disclosure.

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?

One front-loaded sentence plus a compact parenthetical and API-mapping fragment; every element carries information (resource, dashboard alias, meaning, field list, GraphQL source) with no filler.

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, the description appropriately compensates by naming the returned fields, and it explains the passes/Plans naming. The remaining gap is contextual: it does not distinguish this tool from the sibling `memberful_list_plans`, leaving a real ambiguity an agent must resolve.

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 tool takes no parameters, so the baseline is 4. The description instead documents the output fields (id, name), which is the only semantic content available for a parameterless tool.

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?

Names a specific verb and resource ('List all passes') and, critically, disambiguates the terminology: passes are the dashboard's 'Plans' — the access groups a member subscribes to. That mapping is genuinely clarifying. The unresolved issue is that a sibling `memberful_list_plans` exists and the description never says how it differs from this passes listing.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives. Given that `memberful_list_plans` is a sibling and this description explicitly equates passes with 'Plans', an agent has no stated rule for choosing between the two near-identical-looking tools.

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