sonarr_get_delayprofile

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

The readOnlyHint annotation already indicates a safe read operation, so the description's job is to add behavioral context beyond that. It doesn't disclose anything extra, such as response format, possible errors, or rate limits. The phrase 'Fetch a single' hints at the return shape but adds little beyond the tool name and schema.

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 at six words, with no filler. However, the grammatical issue 'delay profiles' (should be singular) is a minor quality flaw, and the structure is a bare phrase rather than a well-formed sentence.

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?

This is a simple getter with one parameter, an output schema, and a read-only annotation, so the baseline expectations are lower. Still, the description omits any context about what a delay profile is or when it's appropriate to retrieve one, leaving the agent to rely on sibling tool names and prior knowledge.

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?

With only one parameter, id, and 0% schema description coverage, the description must compensate by explaining the parameter's meaning. It merely says 'by id', which adds no real value over the schema's integer type and the parameter name. There is no guidance on where the id comes from or what values are valid.

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 states the action 'Fetch' and the resource 'delay profiles', and the qualifier 'single ... by id' distinguishes it from sonarr_list_delayprofile which retrieves all profiles. However, it doesn't elaborate on the nature of delay profiles, making it slightly less informative than a fully distinguishing description.

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 versus alternatives like sonarr_list_delayprofile or sonarr_update_delayprofile. There is no mention of prerequisites or context, leaving the agent to infer usage from the name alone.

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