sonarr_get_system_task_by_id

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

The readOnlyHint annotation already signals a safe read operation, and the description's 'Fetch' is consistent with that. No additional behavioral detail (e.g., error cases, pagination, response format) is provided, so the description adds minimal value beyond the annotation.

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?

One short sentence, front-loaded and free of filler. It earns high marks for conciseness, but the typo ('tasks' for 'task') is a minor quality flaw.

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 fetch-by-id operation with one parameter and an output schema available, the description is sufficient for core understanding. The main missing element is explicit reference to the sibling list tool, which would improve completeness, but the tool's simplicity makes this a minor gap.

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%, so the description bears responsibility for clarifying the 'id' parameter. It only says 'by id' without explicitly stating it is the scheduled task's unique identifier. While this is inferable from the tool name and context, the description itself adds little semantic meaning.

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 the specific verb 'Fetch' with a clear resource ('scheduled tasks') and the qualifier 'by id,' which clearly distinguishes it from the sibling list tool sonarr_get_system_task. The grammatical error ('tasks' instead of 'task') is minor and does not affect clarity.

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 explicit guidance on when to use this tool versus the likely list-all sibling sonarr_get_system_task. The phrase 'by id' implies a specific-id use case, but no exclusions or alternatives are stated, leaving the agent without clear decision support.

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