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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine beyond-annotation context: it specifies that only canonical public feeds are reachable and explicitly excludes private member feeds and authentication. That scoping is the kind of behavioral disclosure that helps an agent avoid wasted calls.

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 with zero filler. The core capability is front-loaded, with the input requirement and exclusion notes following, so the agent gets scope before constraints.

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-value explanation is unnecessary, and the description covers the key scope and constraint facts. It is nearly complete for a two-param read tool; the only mild gap is not pointing to a sibling for private-feed or creator-metadata needs.

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 schema already documents both params as 'Required numeric Patreon ... id' with examples. The description only restates that the ids are numeric and required, adding no syntax, format, or sourcing guidance beyond the schema. 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 (get) and resources (podcast channel metadata and episodes from Patreon's public RSS feed), which is reasonably distinct from siblings like patreon_creator and patreon_creator_tiers. It lacks explicit differentiation from those siblings, so an agent must infer the split from the 'public RSS feed' framing rather than being told.

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?

The description gives a usable boundary — 'private member feeds, authentication parameters, and arbitrary feed URLs are not supported' — which tells the agent this tool only serves public feeds. However, it never names the alternatives (patreon_creator, patreon_explore) or states when this tool should be preferred over them, leaving the routing decision implicit.

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