update_library_clean_bundles

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

Annotations carry most of the behavioral burden (idempotent, non-read-only, openWorld), but the description adds no side-effect detail beyond the word 'clean'. An agent cannot know what changes, whether it triggers background work, or what 'bundles' refers to. No annotation contradiction is present.

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 text is very short and front-loaded with the action; the HTTP path is redundant but harmless. This is concise rather than bloated, though it sacrifices substance.

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 no-parameter maintenance operation, one sentence could be enough, but 'Clean bundles' does not explain the operation's effect, target, or prerequisites. The output schema reduces the need to describe return values, but the missing behavioral context makes the description incomplete.

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 and the input schema is empty, so there are no parameter semantics for the description to add. The baseline of 4 applies.

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 repeats the tool name's phrase ('Clean bundles.') and adds only the raw HTTP path, providing no definition of what cleaning bundles entails or what scope it covers. It does not distinguish this operation from nearby maintenance tools like update_library_optimize or delete_library_caches.

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 when-to-use guidance, prerequisite, or comparison to alternatives. Given hundreds of sibling tools and multiple library maintenance operations, an agent receives no help selecting this tool over others.

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