delete-models-by-collection-id

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Remove models' implies a destructive mutation, but the description doesn't specify whether this is reversible, requires permissions, affects other data, or has side effects. For a deletion tool with zero annotation coverage, this leaves critical behavioral traits undisclosed.

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 description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and target, making it easy to parse quickly. Every word contributes directly to understanding the tool's function.

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 mutation tool with no annotations, no output schema, and incomplete parameter documentation (50% coverage), the description is inadequate. It lacks behavioral context (e.g., permanence, errors), usage guidance relative to siblings, and details on parameters like 'modelIds'. Given the complexity and risk of deletion operations, more completeness is needed.

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 50% (only 'collectionId' has a description), and the description doesn't add any parameter details beyond what's implied by the tool name. It mentions 'from a specific collection' which aligns with 'collectionId', but doesn't clarify 'modelIds' (e.g., format, constraints). With moderate schema coverage, the baseline is 3 as the description provides minimal additional value.

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 'Remove models from a specific collection' clearly states the action (remove) and target (models from a collection), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'delete-models-by-model-id' or 'delete-assets-by-collection-id', which would require specifying it's about removing multiple models from a collection rather than deleting individual models or other resource types.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling deletion tools (e.g., 'delete-models-by-model-id', 'delete-assets-by-collection-id'), there's no indication of whether this is for bulk removal, specific use cases, or prerequisites. The agent must infer usage from the name and parameters alone.

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