sonarr_get_config_downloadclient_by_id

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds no further behavioral context (e.g., error handling, return format) beyond what the annotations and output schema provide. It is consistent with the annotation, but no extra insight is offered.

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 a single, focused sentence with no fluff. Every word contributes to conveying the action and target.

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 simplicity of the operation (one required id, read-only, output schema present), the description is complete enough. The agent can confidently invoke this tool to retrieve a specific config, and the output schema will document the expected response shape.

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 a single 'id' parameter with zero description coverage. The phrase 'by id' provides minimal semantic help—it confirms the id is used to select the config but does not elaborate on what the id refers to, though the tool name and resource type make it inferable. The description adds only marginal value over the schema.

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), resource (download client config), and scope (by id). It distinguishes from the sibling tool 'sonarr_get_config_downloadclient' which likely lists all configs, and from 'sonarr_get_downloadclient' which retrieves a download client entity rather than config.

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 clearly implies when to use this tool: when you need a single download client config identified by its id. It does not explicitly mention alternatives or exclusions, but the context is unambiguous given the tool name and sibling structure.

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