sonarr_get_notifications

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

No annotations are provided, so the description carries the full burden. It says 'List' implying a read-only operation, but it does not explicitly state safety, return format, or any edge cases. The description offers some context with 'all configured' but remains minimal on behavioral details.

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 a single, front-loaded sentence that immediately identifies the verb and resource. It includes parenthetical examples for clarity without unnecessary length. Every word serves a purpose.

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 no parameters and no output schema. The description clearly states what the tool does and gives examples of provider types, which is adequate for a simple listing operation. It could mention that it returns configuration details, but the absence is not a significant gap given the tool's simplicity.

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?

There are zero parameters, so the schema is trivial. The description adds no parameter-specific info, but none is needed. With 0 params, the baseline is 4, and the description adequately covers the tool's purpose without parameter ambiguity.

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 'List all configured notification providers in Sonarr' with a specific verb and resource, and includes examples ('webhooks, email, Slack, etc.') that clearly distinguish it from sibling tools like sonarr_get_quality_profiles or sonarr_get_download_clients.

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 context is clear: this tool is for listing notification providers. However, it does not explicitly state when to use it over alternatives or mention exclusions. For a simple list tool, the purpose alone provides sufficient guidance.

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