sonarr_create_rootfolder

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

The description says 'WRITE: this modifies your Sonarr instance,' which is redundant with the readOnlyHint=false annotation. It doesn't disclose specifics like filesystem effects, validation requirements, or response behavior beyond the output schema.

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 very short and front-loaded with the action. The WRITE warning earns its place, though the brevity sacrifices essential detail. It is appropriately sized for a simple tool but under-specified.

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 single parameter with no schema documentation, the description is insufficient for an agent to invoke the tool correctly. The output schema covers the response but the request body is opaque, and no usage context is provided.

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 only parameter 'body' has no description in the schema (0% coverage) and the description doesn't explain its structure. An agent cannot infer what fields are needed to create a root folder, such as path or name.

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 'Create root folders' with a specific verb and resource, clearly distinguishing it from sibling tools like list/delete/get rootfolder. It is unambiguous and immediately conveys the tool's function.

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 guidance is provided about when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or when to prefer another tool, leaving the agent without explicit usage context.

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