sonarr_update_delayprofile

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

The description explicitly states this is a WRITE operation that modifies the Sonarr instance, which adds a clear mutating context. It aligns with the readOnlyHint=false annotation and does not contradict it, but it provides little extra beyond what the annotation already conveys.

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 with no wasted words, making it concise and front-loaded. However, its brevity sacrifices critical detail, so it earns a high score for structure but not perfection.

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?

The tool has a free-form body object and an output schema, yet the description gives no guidance on constructing a valid update request. It doesn't mention which delay profile attributes can be modified, how to obtain the id, or any side effects beyond generic modification, making it incomplete for real usage.

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 description provides no explanation of the 'id' and 'body' parameters. With schema description coverage at 0%, the description completely fails to clarify what the id identifies or what the body should contain, leaving the agent without necessary semantic information.

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 (update) and resource (delay profiles), distinguishing it from sibling tools like create/delete/reorder. However, it lacks detail on what fields or settings can be updated, so it is clear but not thorough.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus creating, deleting, or reordering delay profiles, nor any prerequisites or workflow context.

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