sonarr_update_notification

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description's WRITE warning adds context that it modifies state. However, it does not detail what specific behavioral aspects (e.g., partial updates, required fields, effects) beyond 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?

Single sentence that is concise and front-loaded with the purpose. The WRITE warning is useful and terse.

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 3 parameters, one required, with nested object and output schema. The description is minimal but mentions WRITE. Given the complexity, more detail could be provided (e.g., how body works, force_save effect), but the output schema likely documents return. Still, for a write operation, the description could be more complete.

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?

Schema description coverage is 0%, so description must compensate. The description mentions 'update notification providers' but doesn't explain the parameters (id, body, force_save). However, the schema has default for body and force_save, but no semantic meaning beyond that. The description adds little beyond what the schema already suggests.

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 states it updates notification providers, which is a specific verb+resource. However, it doesn't distinguish from create/delete notification tools, but the verb 'update' plus the resource 'notification providers' is clear.

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 guidance on when to use vs alternatives. The sibling list includes related notification tools (create, delete, get, list), but the description provides no context for choosing update over create or other actions.

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