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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description reinforces this with 'It reaches no one and changes nothing' and adds the auth requirement ('Needs the user's Cotlet API key with access to this app'). It also notes column composition, which is useful behavioral context beyond the annotations.

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?

Purpose and output format are front-loaded, followed by behavioral and auth details. It is slightly chatty ('It reaches no one and changes nothing') but every sentence carries information.

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?

There is no output schema, and the description compensates by explaining the return is a download link with specific columns, which is exactly what an agent needs. The auth prerequisite is also stated, leaving little an agent needs missing.

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 100%, so paid, status, and tier_id are already fully documented in the schema. The description refers generically to 'the filters you pass' without adding syntax or semantics beyond the schema, so the baseline 3 applies.

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 and resource (export members) plus the output format (CSV download link) and the source (Relationship manager). An agent can distinguish this from the sibling patreon_list_members, which merely lists members rather than producing a downloadable file.

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 explains the tool mirrors the Relationship manager export button and applies the passed filters, which implies its use case. However, it never states when to choose this over patreon_list_members or when to prefer an on-screen list versus a file export.

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