Delete Library

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that – it does not state that the deletion is irreversible, what happens to dependent resources, or any auth/permission requirement, so it earns no credit for added behavioral context.

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, but its brevity reflects under-specification rather than efficient information density. There is no front-loaded constraint or qualifier worth preserving.

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 single-parameter destructive operation the required inputs are covered by the schema and annotations, but the description omits the one thing that matters most for a delete tool: that the action is permanent and unrecoverable. Nothing tells the agent to confirm or to verify the target library first.

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% and the single library_id parameter is documented in the schema as "Library ID to delete." With one fully-described parameter and no additional syntax to convey, the baseline 3 applies; the prose adds nothing further.

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?

"Delete a library" is a bare restatement of the tool name and title, adding no scope, conditions, or distinction from the many other delete_* siblings (mistral_delete_agent, mistral_delete_conversation, mistral_delete_file). An agent learns nothing here it could not infer from the 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?

No when-to-use, when-not-to-use, or alternative is given. It never says that this permanently removes models/assistants attached to the library or points to mistral_list_libraries / mistral_get_library as the lookup steps before deletion.

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