list_providers_episodes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the GET endpoint and the notion of manual search, but provides no additional behavioral detail such as pagination, rate limits, or result characteristics. It does not contradict the annotations.

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 short and front-loaded with the core purpose and endpoint. The 'Args' block is minimal and useful, though a minor grammatical issue ('an episode subtitles') keeps it from being perfect.

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 simple one-parameter GET tool with an output schema and annotations covering read-only/idempotent behavior, the description is largely sufficient. It includes the endpoint and parameter, though it could benefit from a brief usage note or clarification of what 'manually' means.

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 description coverage is 0%, so the description carries the burden of explaining the parameter, but it only restates 'episodeid: Episode ID' — essentially repeating the schema's title. It adds no insight about the expected format, optionality, or consequences of omitting the parameter.

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 ('Search') and resource ('episode subtitles'), and identifies the HTTP endpoint. It is clear about what the tool does, though it does not explicitly differentiate itself from sibling tools like list_providers_movies or list_providers.

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?

No guidance is provided about when to use this tool versus alternatives. The word 'manually' implies a search action, but there is no stated context, exclusions, or comparison to siblings.

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