radarr_list_extrafile

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

Annotations already declare readOnlyHint=true, and the description's 'List' verb is consistent. However, the description adds no behavioral context beyond what the annotation provides, such as filtering behavior, pagination, or scope. It does not contradict the annotations but fails to add value.

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 highly concise with two short sentences: 'List extrafile.' and 'Query params: movie_id.' There is no fluff or redundancy, making it efficient and front-loaded.

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 is minimal and fails to explain what 'extrafile' represents or the significance of movie_id. With an output schema present, return values are covered, but the tool's overall purpose and parameter usage remain ambiguous. Given the tool's likely context (Radarr movie extra files), the description is insufficiently complete.

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 parameter movie_id has no description, and schema coverage is 0%. The description merely restates 'Query params: movie_id' without explaining the parameter's purpose, whether it is optional, or how it affects the result. This is insufficient for the agent to understand how to use the parameter effectively.

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 'List extrafile' which is a clear verb+resource pairing. It is distinct from sibling tools as there is no other 'extrafile' tool, making the purpose clear. However, it lacks any elaboration on what 'extrafile' refers to, preventing a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions. The phrase 'Query params: movie_id' offers no usage context beyond the parameter itself.

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