create_providers_episodes

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, which align with the description's 'download' action. The description adds the endpoint and parameter details but does not elaborate on side effects, required authentication, or the nature of the download (e.g., immediate vs queued). It adds some value beyond annotations but not rich behavioral context.

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 concise, with a one-line purpose followed by the endpoint and a structured Args list. It is front-loaded and avoids unnecessary prose, though the Args formatting is a bit informal.

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 description covers the endpoint, all parameters, and the output schema exists to define the return value. It does not mention prerequisites like provider existence or authentication, but these are likely implied by the system context. The coverage is adequate for calling the tool 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 0% description coverage, so the description's Args list is essential. It explains all 7 parameters, including allowed values for hi, forced, and original_format, and clarifies that 'subtitle' is an ID from a previous GET. This adds significant meaning beyond the bare schema types.

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 the action 'Manually download an episode subtitles' and provides the POST endpoint, which distinguishes it from list/delete siblings. It is specific about the resource (episode subtitles) but does not explicitly mention the provider context, though the name implies it.

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 gives no guidance on when to use this tool versus alternatives like create_episodes_subtitles or create_providers_movies. There are no exclusions or conditions, leaving the agent to infer the appropriate context from the name alone.

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