sonarr_list_releaseprofile

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

The readOnlyHint annotation already communicates that this is a safe read operation, and the description adds no further behavioral details. Since annotations cover the safety profile and the operation is straightforward, the minimal transparency is acceptable but does not go beyond the structured data.

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, using only two words to convey the purpose. There is no unnecessary information, and it is front-loaded with the action and resource.

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?

For a simple list operation with no parameters, a read-only annotation, and an existing output schema, the description is complete. The agent can correctly invoke this tool based on the provided information alone.

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 no parameters to describe, so the description's silence on parameters is appropriate. The empty input schema confirms this, and with zero parameters the baseline score is 4.

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 uses a specific verb ('List') and resource ('release profiles'), clearly indicating a read operation that returns a collection. It distinguishes itself from sibling tools like create, update, get, and delete release profiles, as 'list' implies fetching all.

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 explicit guidance is provided on when to use this tool versus alternatives, such as get_releaseprofile for a single profile. However, the zero parameters and the 'list' prefix imply it retrieves all release profiles, making the usage context reasonably clear by implication.

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