sonarr_root_folders

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

With no annotations, the description carries the burden of disclosing behavior. It states the tool lists root folders and hints at the output being paths, but does not mention any behavioral traits like read-only nature, authentication requirements, or error handling. The output schema may fill some gaps, but the description itself is sparse.

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 that efficiently conveys the tool's purpose and a key usage hint. Every word is necessary with no redundancy.

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 (0 parameters, simple listing operation, and an output schema presumably documenting the return structure), the description is fully complete. It tells the agent exactly what the tool does and why it matters, requiring no further elaboration.

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 no parameter documentation is needed. The description adds value by explaining the purpose of the output (path needed for sonarr_add_series), which aids the agent in understanding how to use the results. Schema coverage is 100% trivially.

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?

Description clearly states it lists configured root folders in Sonarr and explicitly mentions its use case for sonarr_add_series. It distinguishes from siblings by specifying 'in Sonarr' and using a unique verb+resource.

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 when to use the tool (before adding a series) by noting the path is needed for sonarr_add_series. However, it does not explicitly state when not to use it or mention alternatives, though alternatives are minimal.

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