cleanuparr_update_queue_rule

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

Annotations already declare destructiveHint=true, and description's 'Replace' aligns with that. Description adds little behavioral detail beyond field categorization; no side effects or permissions are disclosed. With the destructive annotation present, the minimal extra context is acceptable.

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?

Two sentences, immediately action-focused, and packs the essential field distinctions without waste. Every sentence serves a purpose.

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?

Adequate for a simple update but missing usage context: no mention of where rule_id comes from, no exact values for kind, and no explicit guidance on when to use this vs create/delete. The output schema and destructive annotation cover some gaps, but the description alone leaves 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?

With 0% schema description coverage, the description compensates by enumerating fields for stall (minimumProgress) and slow (minSpeed, maxTimeHours, ignoreAboveSize) rule types. It adds meaning to the opaque 'rule' object and implies that 'kind' selects stall/slow. However, does not define field semantics or rule_id.

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?

Clearly states the action ('Replace') and resource ('stall or slow queue rule'), distinguishing from sibling create_queue_rule/delete_queue_rule. The verb and field categories make the tool's scope explicit.

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?

Implies usage via replacement of existing stall/slow rules, but provides no explicit when-to-use guidance or alternatives. Sibling create/delete operations are not mentioned, leaving the user to infer when this tool is appropriate.

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