sonarr_create_delayprofile

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

The annotations already indicate readOnlyHint=false, but the description adds a clear warning 'WRITE: this modifies your Sonarr instance'. This reinforces the write nature and alerts the agent to side effects, going beyond the annotations. There is no contradiction with the annotations.

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 concise, consisting of two sentences. Purpose is front-loaded and the write warning is a single additional sentence. Every word earns its place.

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 is a creation operation with a completely unspecified request body. The description does not mention required fields or configuration options, making it insufficient for an agent to invoke correctly. Sibling tools like sonarr_get_delayprofile could provide more context, but the description doesn't point to them.

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 only a free-form 'body' object with additionalProperties true and 0% schema description coverage. The description provides no details about what fields the delay profile body should contain, leaving the agent completely without guidance for constructing the request.

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 'Create delay profiles', using a specific verb and resource. This distinguishes it from sibling tools like sonarr_update_delayprofile, sonarr_delete_delayprofile, and sonarr_list_delayprofile.

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 does not provide any guidance on when to use this tool versus alternatives. It only says 'Create delay profiles', without mentioning when not to use it or pointing to sibling tools for other operations.

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