Api stored libraries batch action create

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the description's main job is to explain what the batch payload does. It adds nothing: no list of supported actions, no all-or-nothing semantics, no failure behavior, no note that the endpoint is non-idempotent and re-running may duplicate effects.

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 short sentence with no wasted words, and nothing is buried. The problem is under-specification rather than verbosity, so it is efficient but content-free.

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 non-idempotent mutation endpoint with a free-form body and no output schema, the description should explain the action model and payload contract. It explains neither, so an agent cannot call this correctly without guessing.

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 parameter is an untyped free-form `body` object with 0% schema description coverage and 0 required fields. The description supplies no hint about the expected payload shape — action verb, object IDs, or selection criteria — leaving the agent with no way to construct a valid call.

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 sentence restates the name's generic skeleton ("batch action on multiple objects") without naming the resource actually being acted on — stored libraries. With roughly a hundred sibling *_batch_action_create tools sharing this identical wording, an agent cannot tell which entity this operates on from the description 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 indication of when to use this versus the per-object create/update/destroy siblings, nor what prerequisites (permissions, loaded library state) apply. The word "batch" implies multi-object use but no alternative or exclusion is named.

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