radarr_create_indexer

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

Annotations already indicate readOnlyHint=false, and the description reinforces with 'WRITE: this modifies your Radarr instance'. This adds a warning about side effects, but doesn't detail what exactly gets modified, prerequisites, or required permissions. Beyond the annotation, it adds little.

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 only two sentences, front-loaded with the action verb and a short warning. It is efficient and has no wasted words, though it could have included more detail without losing conciseness.

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 creation tool with an open 'body' object and no parameter descriptions, the description is severely incomplete. It doesn't reference how to structure indexer configuration, what fields are required, or that force_save affects validation. The existence of radarr_get_indexer_schema is not hinted at, leaving the agent without sufficient context.

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 input schema has 0% description coverage for its two parameters. The description provides no explanation of 'body' (an open object) or 'force_save' (a boolean). This leaves the agent without any guidance on what content to provide.

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 the verb 'Create' with the resource 'indexers', clearly identifying the action. It distinguishes from sibling tools like update_indexer, delete_indexer, and list_indexer. The WRITE modifier adds clarity about its mutating nature.

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 states 'Create indexers' and warns 'WRITE: this modifies your Radarr instance', giving clear context that this is for creating new indexers. It doesn't explicitly mention alternatives or when-not-to-use, but the action is unambiguous among siblings.

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