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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the data is generated from the publisher's feed, enriched from rssamplifier.com, and corrected by the claimant, and the response is Markdown plus the serving URL. It does not mention auth needs, caching or rate limits, so it stops short of a 5.

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?

It is a single dense paragraph, front-loaded with the resource and return shape, and every clause carries information (fields, provenance, return value). The embedded URLs and the booking-platform aside add length without much operational value, keeping it from a 5.

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?

There is no output schema, and the description does its part by stating that it returns Markdown plus the URL the file is served at. However, for a one-parameter lookup tool the sole parameter is left entirely undefined, so an agent still lacks what it needs to call it correctly.

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?

The schema has one required parameter, 'slug', with 0% description coverage, and the description never mentions it. It is unclear whether the slug identifies a show, a person, or a domain-qualified key, which is exactly the kind of ambiguity that causes mis-invocation. The description's rich content about the returned document does not compensate for this gap.

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?

The description states a specific verb and resource: it returns the person or organisation behind a show as an OpenProfile.md, with an explicit enumeration of the Broadcast section fields (name, kind, site, avatar, accounts, topics, feed, cadence, language, since). That is far more specific than the title alone. It does not name a sibling tool to contrast with (e.g. p0dcasters_get_podcast), so the agent must infer the boundary itself.

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?

One use case is implied: 'A booking platform matches a Broadcast section against a guest's Guest section', which signals a matching/verification scenario. There is no explicit statement of when to call this versus the show-level or feed-level siblings, and no prerequisites or exclusions. Usage is inferable but not spelled out.

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