episodes_live

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

Annotations already declare readOnlyHint=true, so the safety profile is clear. The description adds that it gets episodes 'currently live' and 'across the Podcast Index', providing more context on the scope of the data. However, it does not disclose potential rate limits, response format, or any other behavioral traits beyond what annotations already cover.

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?

The description is two sentences long, front-loaded with the key purpose, and every sentence provides value. No unnecessary words.

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?

The tool has no output schema, so the description should ideally explain what fields the response contains. It only states that it returns 'episodes that are currently live' without any structural detail. For a simple list tool, this might be acceptable, but it leaves agents guessing about the response format. Additionally, it does not mention any pagination or limitations beyond the 'max' parameter.

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% because the only parameter 'max' has a description in the schema. The tool description does not add any additional meaning beyond the schema. With high coverage, baseline score is 3, and description does not elevate it.

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 clearly states it retrieves episodes that are currently live across the Podcast Index. It uses a specific verb ('Get'), specifies the resource ('episodes'), and adds a distinguishing qualifier ('currently live'). This helps differentiate from siblings like 'recent_episodes' which return recent episodes regardless of live status.

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 includes a usage hint ('Useful for finding live shows in progress'), which implies when to use the tool. However, it does not explicitly state when not to use it or mention alternatives. Still, the context is clear enough for an agent to decide.

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