sonarr_get_rootfolder

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

The annotation readOnlyHint=true already signals a safe read operation, and the description simply says 'Fetch' without adding further context such as error behavior, authentication requirements, or pagination. The description is consistent with annotations, so no contradiction, but it adds no behavioral insight 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 sentence with no wasted words. It is front-loaded with the verb 'Fetch' and immediately states the resource and lookup key, making it highly scannable.

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 get-by-id tool with one parameter and an output schema (though not shown), the description sufficiently conveys the operation. The slight grammar error and lack of mention of possible null return when not found are minor gaps, but overall the tool is adequately specified.

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?

Schema description coverage is 0%, so the description must compensate. The phrase 'by id' confirms the role of the 'id' parameter but does not specify that it refers to the root folder ID or provide any type/format details. Given only one parameter, this is minimally adequate but not rich.

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 uses a specific verb 'Fetch' and clearly identifies the resource as a single root folder by id, distinguishing it from sibling tools like list_rootfolder, create_rootfolder, and delete_rootfolder. The grammar issue ('folders' instead of 'folder') does not obscure the meaning.

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 implies usage for retrieving a specific root folder by its id, but does not explicitly state when to use this versus alternatives (e.g., list_rootfolder for all). No exclusions or prerequisites are mentioned, so guidance is minimal but not misleading.

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