sonarr_get_releaseprofile

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

The `readOnlyHint: true` annotation already covers safety, but the description adds no behavioral context beyond repeating the tool name. No mention of error responses (e.g., 404 if not found), return format, or any side effects.

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?

A single sentence that is front-loaded and free of filler. The minor grammar issue ('profiles' should be singular) does not hinder clarity.

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 get-by-id tool with one integer parameter, an output schema, and a read-only annotation, the description is largely sufficient. It tells the agent exactly what to do; the output schema accounts for return values.

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% and the lone parameter `id` is bare. The description's 'by id' clarifies that the parameter is the release profile id, but it does not elaborate on the id's source or constraints. This is minimal compensation.

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 ('Fetch') with a clear resource ('release profile') and scope ('a single ... by id'). It clearly distinguishes from sibling `sonarr_list_releaseprofile`, which presumably returns multiple profiles.

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 implies usage for a single resource via the word 'single' and the contrast with the sibling list tool, but it does not explicitly state when to use this versus `sonarr_list_releaseprofile` or mention any exclusions.

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