radarr_create_releaseprofile

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's statement 'WRITE: this modifies your Radarr instance' merely restates the annotation without adding new context. No additional behavioral details are provided (e.g., side effects, required permissions, or idempotency).

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 extremely short and front-loaded, conveying the core action in four words. The WRITE warning adds a necessary caution but otherwise the text is minimal and free of fluff. Slightly more detail would be useful, but it is not verbose.

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 involves a complex operation (creating a release profile) with an arbitrary body parameter. The description lacks any context about the payload structure, required fields, or how to obtain a schema template. It is inadequate for an agent to construct a correct request.

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 single 'body' parameter with additionalProperties=true and 0% description coverage. The description provides no field names, structure, or examples for building a release profile body, making it impossible to know what payload to supply.

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 release profiles' uses a specific verb ('Create') and a clear resource ('release profiles'), which unambiguously distinguishes it from sibling tools like list, update, or delete release profiles. The action is immediately understandable.

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, no prerequisites, and no mention of related tools such as update or get release profile. The only extra sentence is a WRITE warning, which is a caution, not a usage guideline.

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