delete_all_models_api_v1_models_delete_all_delete

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

No annotations provided, so description must fully disclose behavior. It only states 'Delete All Models', omitting that this is destructive, irreversible, may require admin privileges, and lacks any safety warnings or side effects. This is a high-risk operation with insufficient transparency.

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?

Extremely concise (3 words), but at the expense of critical context. While brevity is good, it sacrifices meaningful information that an agent needs to safely invoke this tool.

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 destructive tool with no annotations, output schema, or parameter details, the description is severely incomplete. It fails to specify who can execute it, whether it's reversible, what happens to associated data (e.g., chats using models), and any confirmation or rollback mechanism.

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?

No parameters exist, so schema coverage is 100% trivial. Description adds no value beyond the schema; it merely restates the function name. A baseline of 3 is appropriate for zero parameters with no additional clarity on scope or operation.

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?

Description clearly states verb 'Delete' and resource 'All Models', distinguishing it from siblings like delete_model_by_id which deletes a single model. However, it could specify the scope (e.g., all models in the system vs. user's models).

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 guidance on when to use this tool vs alternatives (e.g., delete_model_by_id). No mention of prerequisites, permissions, or situations where this tool is inappropriate. The sibling list includes a more granular deletion tool, but the description fails to contrast them.

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