radarr_list_rootfolder

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

The annotation readOnlyHint=true already communicates the read-only nature. The description adds no additional behavioral context (e.g., return format, pagination, ordering). This is acceptable for a simple list tool, but it does not go beyond the annotation.

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 a single, clear sentence that efficiently conveys the tool's purpose. It is appropriately sized, though it provides no additional context that might be useful for clarity.

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?

Given the tool's simplicity (no parameters, output schema present, read-only annotation), the description is sufficient for a basic listing operation. It could mention the return structure or the concept of 'root folders', but these are implied by the domain and schema.

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, so there is no need for parameter explanations. The baseline score of 4 applies as the description and schema are fully aligned with no unresolved param details.

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 'List root folders' with a specific verb and resource. It distinguishes from sibling tools like radarr_get_rootfolder, radarr_create_rootfolder, and radarr_delete_rootfolder by implying enumeration rather than retrieval or modification.

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 explicit guidance is provided for when to use this tool vs alternatives. However, the name and description imply its use for retrieving all root folders, and the context of siblings provides enough implicit direction.

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