Api stored libraries unload create

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

Annotations declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, but the description adds nothing about what is mutated, whether the unload is reversible, or what permissions/state are required. For a non-idempotent write operation with an opaque 'body' payload, this is a total absence of behavioral disclosure.

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?

It is extremely short, but this is under-specification rather than conciseness — the single token is a machine-generated slug that conveys no information beyond the tool name itself.

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, open-world create operation with a required id and an opaque body and no output schema, the description should carry nearly the entire burden. Nothing is provided, so an agent cannot safely invoke it.

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 description coverage is 0% for 2 parameters. The required 'id' and the untyped free-form 'body' object are completely undocumented, and the description does not compensate in any way. An agent has no idea what to put in 'body'.

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 is the raw operation identifier 'api_stored_libraries_unload_create' restated verbatim, which is a tautology of the name/title. It gives no indication of what 'unload' does to a stored library, and does not distinguish this tool from siblings like stored_libraries_import_create, stored_libraries_upload_create, or stored_libraries_destroy.

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 guidance whatsoever about when to use this tool, when not to, or which sibling to prefer. An agent cannot infer from 'unload' alone whether this is the inverse of import, a destructive removal, or an unloading into memory.

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