radarr_action_notification

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

Annotations already declare readOnlyHint=false. The description adds an explicit 'WRITE: this modifies your Radarr instance' warning, which is useful but does not elaborate on side effects, reversibility, or required permissions. It adds minimal context 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?

The description is very short, but the first sentence is grammatically awkward and unclear ('on a action'). While concise, it sacrifices clarity and does not front-load useful information effectively.

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 generic action-executor pattern with no enums on name and an opaque body object. The description does not provide valid action values, explain body usage, or tie the tool to notification-specific actions. Output schema exists but does not compensate for missing operational context.

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 the description must compensate. It only clarifies that 'name selects the action' for the name parameter, leaving the body object completely unexplained. This is insufficient for a parameter with arbitrary additional properties.

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 'Run an action on a action' is vague and tautological, failing to identify the target resource (notifications). It says 'name selects the action' but does not clarify what domain the action operates on, making it hard to distinguish from siblings like radarr_action_downloadclient.

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 is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description offers no contextual hints for tool selection.

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