sonarr_create_indexer_test

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

The description adds a 'WRITE: this modifies your Sonarr instance' warning, but this is already implied by readOnlyHint=false in the annotations. It does not disclose any side effects, return behavior, or prerequisites, adding minimal value beyond what the annotations already convey.

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, which is concise, but the first sentence is redundant with the tool name and the second is a generic warning. It is under-specified rather than efficiently complete, so it does not earn a higher score.

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 tool with a nested 'body' object and no parameter documentation, the description is inadequate. The output schema may cover return values, but the input parameters are unconstrained and unexplained, making it difficult for an agent to invoke the tool correctly.

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?

With 0% schema description coverage, the description does not explain the 'body' object or 'force_test' boolean parameter. The schema only lists types and defaults, leaving the agent without guidance on what to provide in the body or how force_test affects behavior.

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 'Create indexer test.' is a direct restatement of the tool name, providing no additional detail about what testing an indexer involves. It also does not differentiate from sibling tools like sonarr_create_indexer_testall, which tests all indexers.

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?

There is no guidance on when to use this tool versus alternatives such as testall or other test tools. The description simply states the action without any context about appropriate usage or exclusions.

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