sonarr_create_indexer

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

Annotations already indicate readOnlyHint=false, implying a write operation. The description repeats this with 'WRITE: this modifies your Sonarr instance' but adds no new behavioral context such as side effects, permissions, or rate limits. With annotations present, the bar is lower, but this description adds minimal value beyond restating 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 concise and front-loaded: 'Create indexers' immediately states the action, followed by a brief warning. Both sentences serve a purpose, and there is no wasted text.

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 create operation with a generic body schema and many sibling tools, the description is incomplete. It does not explain the required structure of the indexer object, the role of force_save, or how this differs from related create actions. The agent would be unable to construct a valid request without external information.

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 schema has a 'body' object and 'force_save' boolean with no descriptions, and schema description coverage is 0%. The description does not explain what should go in the body or what force_save controls, failing to compensate for the lack of schema descriptions.

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 the tool creates indexers with the verb 'Create' and resource 'indexers'. It does not differentiate from sibling tools like sonarr_create_indexer_action or sonarr_create_indexer_test, so it lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives, such as when to use sonarr_list_indexer_schema or sonarr_create_indexer_test. It only states what it does, not the context or prerequisites.

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