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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-facing profile are covered. The description adds that the data is 'public' and that availability flags (membership/RSS) are included, but says nothing about auth needs, rate limits, or how missing/private creators are handled. With annotations doing the heavy lifting, this is adequate but not rich.

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?

Two tight sentences: the primary action and its scope lead, the sibling routing follows. No filler, no restatement of the title or schema.

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?

An output schema exists, so return values needn't be spelled out, yet the description still summarizes the payload, plus it routes to the right siblings. Complete enough to invoke correctly; a minor gap is the absence of any note on behavior for non-existent or private handles.

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% and the single `handle` param is already documented with an example (CachyOS). The description reinforces 'by page `handle`' but adds no format rules or edge-case guidance beyond the schema, so the baseline 3 is appropriate.

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 ('Fetch') and resource ('public Patreon creator-profile metadata') scoped to a `handle`, and enumerates the returned content (identity, summary, images, counts, earnings snapshot, membership/RSS availability). It explicitly disambiguates from cousin tools by name, so an agent can separate it from patreon_creator_tiers without opening either schema.

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?

Directly routes the agent: 'Use patreon_creator_tiers for tiers, patreon_rss for posts, or patreon_explore to discover creators.' This names the alternatives and the condition that selects each, leaving nothing to inference.

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