nzbget_rate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Set download rate limit' implies a configuration change, it doesn't disclose important behavioral traits like whether this is a persistent setting, whether it requires specific permissions, what units the rate limit uses (KB/s, MB/s), or what happens when invalid values are provided. The description is too minimal for a mutation tool with zero annotation coverage.

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 just three words, with zero wasted language. It's front-loaded with the essential action and target. While it may be too brief for completeness, as a standalone statement it's efficiently structured.

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 this is a mutation tool with no annotations, no output schema, and a parameter with 0% schema coverage, the description is incomplete. It doesn't explain what happens after setting the rate limit, what the response looks like, what side effects might occur, or provide enough context for safe and effective use. The extreme brevity leaves too many unanswered questions.

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 0% description coverage, providing no documentation for the 'limit' parameter. The description doesn't compensate for this gap - it doesn't explain what the 'limit' parameter represents, what units it uses, what valid ranges are, or provide any semantic context beyond what's implied by the tool name. For a single required parameter with zero schema documentation, this is inadequate.

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 'Set download rate limit' clearly states the verb ('Set') and resource ('download rate limit'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like nzbget_pause_download or nzbget_resume_download that also affect download behavior, so it doesn't reach the highest score.

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. There are multiple sibling tools that affect downloads (pause_download, resume_download), but the description doesn't explain when rate limiting is appropriate versus pausing/resuming, or whether this tool should be used before, during, or after downloads.

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