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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's 'Read-only' is redundant. However, it adds genuinely new behavioral context: the creator/admin authorization requirement and the fact that archived tiers are excluded unless include_archived is set.

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?

Front-loaded with the core action and the field list, then the include_archived toggle, then the auth requirement. Dense and mostly efficient, though the long field enumeration in the first sentence runs on.

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 usefully enumerates the returned fields, and it covers the authorization requirement and both parameters. Pagination or result-size behavior is not addressed, but for a two-parameter read tool this is close to complete.

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 coverage is 0%, so the description must carry the load. It explains that include_archived surfaces archived tiers and that community_id scopes the request and requires creator/admin rights, giving meaningful semantics for both 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?

States a specific verb (List) and resource (a community's membership tiers), and enumerates the returned fields (name, privileges, pricing, member counts, payout). This clearly separates it from siblings like list_ticket_tiers and list_community_members.

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?

It gives a useful precondition (must be creator or admin) and a usage hint for include_archived, but never states when to prefer this tool over alternatives or when not to call it. Context is implied rather than spelled out.

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