list_episodes

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it only partially meets it. It discloses scope ('all available episodes') but says nothing about return format, ordering, pagination, episode metadata fields, or whether the response could be large. Since there is no output schema to compensate, the agent is left guessing about what the tool actually returns.

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 sentences with zero waste. The purpose is front-loaded in the first sentence, and the second sentence earns its place by adding a usage context. Every word contributes value, and the description is appropriately sized for a zero-parameter tool.

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 zero-parameter list tool, the description is nearly complete for invocation purposes: the agent knows what the tool does and why to call it. The main gap is the absence of any return-value description, and since no output schema exists, a brief note on what the response looks like would have made it fully self-sufficient.

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 tool has zero parameters and an empty schema properties object, so there is nothing the description needs to explain. Per the rubric, 0 params earns a baseline of 4. The description appropriately adds no redundant parameter information because none exists.

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 ('List') and resource ('all available episodes in the Big Technology Podcast archive'), making the tool's function immediately clear. The qualifier 'all available' implicitly contrasts with the sibling get_recent_episodes, though it never names alternatives explicitly. A 5 would require explicit sibling differentiation, so this lands just below.

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 second sentence, 'Use this to see what topics and guests are available to search,' gives a clear use case for the tool as a discovery step before searching. However, it provides no exclusions, no reference to alternatives like search_transcripts or get_episode, and no guidance on when this tool would be the wrong choice. The usage context is implied rather than explicitly routed.

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