list_system_releases

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

The annotations (readOnlyHint, idempotentHint, destructiveHint) already disclose the safety profile. The description adds nothing behavioral beyond the endpoint, and does not mention response behavior, caching, or any special conditions. Since annotations carry the burden, the description contributes no extra value there.

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, just a single sentence and the endpoint. It is front-loaded and free of fluff, which is appropriate for a simple 0-parameter operation. However, it may be slightly under-specified for an agent unfamiliar with the tool's intent.

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?

With an output schema present, the return format is documented. However, the description does not explain the tool's purpose in context (e.g., checking for updates) or how it relates to other system tools. It is minimally complete but lacks enough context to guide appropriate usage.

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, so the schema fully covers the input side. The baseline for 0 parameters is 4, and the description does not need to explain parameter semantics. No additional meaning is required.

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 states a clear verb ('Get') and resource ('Bazarr releases'), and includes the API endpoint which removes ambiguity. It is distinctive enough from sibling tools, though 'releases' could be interpreted as software versions vs. data releases. No other sibling directly targets releases, so the purpose is clear.

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 invoke this tool versus alternatives, nor any mention of prerequisites or expected use cases. The description is purely declarative with no context about why an agent would call it, such as checking for available updates.

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