radarr_create_delayprofile

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds 'WRITE: this modifies your Radarr instance,' which essentially restates the readOnlyHint=false annotation without adding new context like side effects, idempotency, or required permissions. Minimal additional transparency.

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 purpose. The second sentence is somewhat redundant with annotations, but the overall length is appropriate. No wasted words, though information is missing.

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 free-form body and no schema guidance, the description is severely incomplete. The agent cannot know what payload to construct, whether there are constraints, or how the operation behaves. The presence of an output schema helps but is not shown here, and the description does not address it.

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 defines a single 'body' object with additionalProperties: true and no required properties. The description gives zero information about what fields the body should contain or what structure is expected. Schema coverage is 0%, so the description was expected to compensate but fails entirely.

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 verb 'Create' and the resource 'delay profiles', distinguishing it from sibling tools like update, delete, or get. However, it does not elaborate on what a delay profile is or what specific parameters are needed, so it is clear but minimal.

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. It does not mention that updates should use radarr_update_delayprofile, nor does it describe prerequisites or scenarios. The only extra sentence is a warning that it modifies the instance, which is not usage guidance.

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