put_downloads_throttling

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

Without annotations, the description reveals that non-schedule modes persist until changed back to schedule. But it doesn't mention side effects, required permissions, or impact on ongoing downloads. The behavior is partially transparent but incomplete.

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?

Three sentences, somewhat wordy (e.g., 'using this method'). Could be tightened by merging sentences and removing redundant phrasing. Acceptable but not optimally concise.

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 the complexity (4 params, enums, nested objects) and existence of output schema, the description covers the main mechanism but omits details on parameter interactions (e.g., whether normal/slow are ignored when mode is not schedule). Leaves some uncertainty.

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 coverage is 100%, baseline 3. The description adds context on mode values and schedule array behavior, but does not detail how normal/slow objects interact with mode. It adds moderate value beyond the schema.

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 clearly states it's about forcing throttling mode for downloads, using modes from DlThrottlingConfig. It distinguishes between schedule and other modes, but does not explicitly differentiate from sibling tools like put_downloads_config.

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?

It explains when to use 'schedule' vs other modes, and notes that non-schedule modes force until reset. However, it provides no explicit guidance on when to prefer this tool over alternatives, nor any prerequisites or exclusions.

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