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

Annotations already declare the safe/idempotent read profile, so the bar is lower, yet the description still adds real behavior: 'old URLs of moved feeds resolve' and the conditional 'For a signed-in account, also returns your outreach history' tied to auth state. These go beyond what the annotations state.

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?

Front-loaded with the core promise ('One podcast in full') followed by a return-field inventory and input modes. It is dense and long but nearly every clause carries information; minor trimming of the field list is possible.

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?

With no output schema, the description fully carries the burden and does so: it describes returned identity/activity/episode/contact data in enough detail to set expectations, covers the single input's three forms, and notes the auth-conditional outreach history.

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 the schema description already names the three accepted forms, so the baseline is 3. The description adds value by noting that stale feed URLs of moved feeds still resolve, a nuance the schema omits, warranting one step up.

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 ('One podcast in full') and then enumerates exactly what is returned: identity fields, activity status, feed health, latest episodes, and every contact route. This scope is precise enough to distinguish it from find_podcast_contacts and entity_profile 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?

Usage is implied by the reference to 'a show_id from find_podcast_contacts' and by the accepted input forms, suggesting a pipeline role. However, it never states when to prefer this tool over siblings like find_podcast_contacts or entity_profile, nor any exclusions.

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