radarr_list_releaseprofile

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

The description merely restates the read-only nature already captured by the readOnlyHint annotation. It does not add any behavioral details such as ordering, pagination, or what fields are returned. Since annotations already declare read-only, the description adds no incremental information 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 brief at three words, which is appropriately concise for a simple list operation. However, it is almost a verbatim restatement of the tool name, offering little additional information, so it doesn't earn a top score.

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?

Given the tool has no parameters, a readOnly annotation, and an output schema, the description conveys the core function. However, it lacks any context about what the output contains, optional filters, or usage situations, leaving some gaps for an agent deciding between similar list tools.

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 defined in the schema, and the description correctly implies no inputs are needed. With zero parameters, the baseline is 4, and the description does not need to add parameter semantics.

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 a resource 'release profiles', clearly indicating the operation. It distinguishes from siblings like radarr_get_releaseprofile (single) and radarr_create_releaseprofile (write) by the verb and resource, though it lacks additional scope details.

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 description provides no guidance on when to use this tool instead of other list tools (e.g., radarr_list_qualityprofile) or how it relates to radarr_get_releaseprofile. No exclusions or alternatives are mentioned, so the agent receives no decision-making support.

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