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

Goes beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing that the message reaches other people, that a per-call confirmation is on by default and can be disabled for this tool, and that a Cotlet API key with app access is required. These are meaningful operational traits an agent would not otherwise know.

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 is front-loaded, but the confirmation point is stated twice ('By default you confirm each call; you can switch that off' and 'confirm with the user before each call'), and the opening 'The same direct message' is awkward. Roughly one sentence of redundancy.

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 2-param mutation tool with annotations and no output schema, the description covers audience reach, confirmation policy, and auth requirements, which is most of what the agent needs. It omits nothing critical, though it could clarify the relationship to patreon_send_message.

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 100% and both parameters are documented there (body as message text, tier_ids sourced from list_tiers). The description only echoes this ('tiers you name') and adds no syntax, format, or cardinality detail beyond the schema, so 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: sends one direct message to the members of one or more named tiers. However, it does not differentiate from the sibling patreon_send_message (individual member messaging), and the opening phrase 'The same direct message' is vague about what it is the same as.

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?

Gives one real usage constraint ('Only paid members can be messaged'), but provides no explicit when-to-use guidance versus patreon_send_message or any other alternative. The agent must infer that this is the tier-broadcast variant.

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