radarr_get_releaseprofile

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

The annotation readOnlyHint=true already indicates a safe read operation. The description adds no additional behavioral context such as potential 404s, authentication needs, or response handling. It stays consistent with the annotation without adding new information.

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 one short, clear sentence with no redundant filler. It is appropriately sized for the tool's simplicity, despite a minor grammatical error ('profiles' instead of 'profile').

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 read-only fetch-by-id tool with an output schema present and only one parameter, the description is mostly complete. The main missing element is explicit guidance on differentiating this from the list sibling, but that is covered under usage guidelines rather than contextual completeness.

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 schema has one integer parameter 'id' with no description, and the tool description only says 'by id', which barely clarifies its role. Since it is a simple and obvious identifier, this is adequate but does not compensate beyond the name.

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 specifies the action ('Fetch'), the resource ('release profile'), and the scope ('single ... by id'). It distinguishes itself from the sibling tool radarr_list_releaseprofile by focusing on a single item rather than a list.

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 usage is implied: fetch a specific release profile when you know its id. However, it does not explicitly mention when to use this tool over the list alternative or provide any exclusion criteria, so the guidance is minimal.

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