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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully adds that only public data is returned (identity, summary, public earnings snapshot, availability flags), but says nothing about auth requirements, rate limits, or what happens with an invalid/private handle.

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?

A single front-loaded sentence that leads with verb and resource. The trailing field enumeration is somewhat long but doubles as a return-value preview, so it largely earns its place.

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 one-parameter read tool with an output schema and safety annotations, the description is sufficient; return fields are documented structurally, so listing them is a bonus rather than a necessity. Nothing an agent needs to invoke it correctly is 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% and the single handle param already documents the format with an example. The description repeats 'by its page handle' without adding syntax, casing, or URL-vs-handle disambiguation beyond the schema.

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?

Specific verb (Get) plus resource (public Patreon creator profile) and input mechanism (by its page handle), with an enumerated field list. It is clearly distinct from patreon_creator_tiers and patreon_rss by resource, though it never names those siblings to differentiate explicitly.

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?

Only implied usage: supply a handle, receive the profile. There is no statement of when to prefer this over patreon_explore, patreon_rss, or patreon_creator_tiers, and no prerequisites or exclusions are given.

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