set_learning_batch_rate

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuinely useful trait — it returns an actual readback and never silently falls back — plus that the change affects both current and future work. It omits permissions, idempotency, and what a failed set looks like.

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 compact clause-set with the scoping and the readback guarantee front-loaded; no filler. Brevity here costs clarity rather than padding, but structurally it is efficient.

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 mutation tool with no annotations and no output schema, the description leaves out units/range for the rate, what 'current/future' concretely means for running batches, and error behavior beyond 'never silent fallback'. Not enough for an agent to call it confidently.

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 single 'rate' parameter has 0% schema description coverage: no units, no valid range, no explanation of the 1.25 default. The description adds nothing beyond the word 'rate', so the low-coverage gap is not compensated.

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 verb 'Set' and the object 'rate' are present, but the description says only 'this account's current/future rate' without saying what kind of rate (learning batch pacing?) or how it differs from siblings like set_owned_video_rate and set_parallel_playback_rate. An agent must infer the resource from the tool name alone.

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 statement of when to use this versus the closely-named set_owned_video_rate or set_parallel_playback_rate, nor any prerequisite such as an active batch. Usage is only implied by the name.

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