radarr_create_qualityprofile

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

The annotations already indicate a write operation (readOnlyHint=false). The description's additional 'WRITE: this modifies your Radarr instance' merely restates this without adding new behavioral context like idempotency, validation requirements, or side effects.

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 two short sentences, front-loaded with the core action. Every word contributes to clarity, and there is no unnecessary verbiage.

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?

Despite having an output schema, the tool requires a complex body parameter that is entirely undocumented in both the schema and description. The description does not point to radarr_get_qualityprofile_schema or outline required fields, making it inadequate for agent execution.

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 a single 'body' object with no property definitions or descriptions (0% coverage). The description provides no guidance on what the body should contain or how to construct a valid quality profile, failing to compensate for the schema's lack of detail.

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 action (create) and the resource (quality profiles). It effectively distinguishes this tool from siblings like radarr_list_qualityprofile, radarr_update_qualityprofile, and radarr_get_qualityprofile.

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 use when creating a new quality profile, but does not explicitly contrast with updating or retrieving. No exclusions or alternative tool references are provided, leaving the usage context largely implicit.

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