sonarr_get_config_mediamanagement

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

The description adds no behavioral details beyond what the readOnlyHint annotation already provides. It does not mention the response format, whether the config is the full set, or any edge cases. Since annotations cover the read-only safety profile, the description contributes no extra transparency.

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 concise sentence, front-loaded with the action and resource. Every word earns its place, and there is zero redundancy or unneeded detail.

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 list tool with no parameters and an output schema present, the description is largely complete. However, it could be improved by explicitly stating that it returns all media management config (for contrast with the _by_id variant), though the verb 'List' already implies this.

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 tool has zero parameters and an empty input schema, so there are no parameter semantics to explain. The baseline for 0 parameters is 4, and the description accurately reflects the no-input nature without needing to compensate for missing schema coverage.

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 resource ('media management config'), clearly indicating this retrieves the full configuration. The plural 'List' distinguishes it from sibling 'sonarr_get_config_mediamanagement_by_id' which fetches a single item, so the purpose is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives such as the _by_id variant or update tool. The name implies a 'list all' operation, but the description does not explicitly state exclusions or conditions, leaving the agent to infer usage from tool naming alone.

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