sonarr_push_release

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

Annotations already provide readOnlyHint=false and destructiveHint=false. The description adds 'WRITE: this modifies your Sonarr instance,' which is a generic warning and adds only marginal context beyond the annotations. It does not disclose details about permissions, reversibility, or what specifically gets modified.

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 exceptionally concise: two short sentences, with the action front-loaded. Every word contributes to conveying the tool's purpose and write nature, with no redundancy.

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's invocation is undermined by the completely unspecified body parameter and absence of usage context. An agent cannot reliably construct a valid request without additional knowledge about what a 'release' object entails.

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 contains only a single 'body' object with additionalProperties=true and no documented internal properties. Schema description coverage is 0%, and the description does not explain what should be placed in the body (e.g., release title, download URL). The agent is left without meaningful parameter guidance.

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: 'Push a release to the download client.' It specifies a concrete verb and resource, making the core purpose unambiguous. However, it does not explicitly distinguish this from other release-related tools like sonarr_grab_queue_item or sonarr_search_releases, so it stops short of a perfect score.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention prerequisites, typical workflows, or when a different tool (e.g., search_releases, grab_queue) would be more appropriate.

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