category_collection_remove

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

It discloses that the operation cannot be undone and may cause errors if the category is referenced by collections. However, it lacks details on authorization, rate limits, or other behavioral traits that are not covered by annotations (none provided).

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 concise, with two sentences and a list of arguments. It is front-loaded with the purpose and every sentence adds value without unnecessary detail.

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 deletion tool, it covers irreversibility and potential side effects. It is sufficiently complete given the presence of an output schema (though not shown) and distinct sibling tools.

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 description restates the parameters with their enum values and descriptions, which match the schema. Since schema coverage is 100%, the description adds no new meaning beyond what the schema already provides.

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 clearly states the action (remove), the resource (category or collection), and scope (from current project). It distinguishes from sibling tools like add, change, update, and list, making its purpose unambiguous.

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 a caution about potential errors if removing a referenced category, but does not explicitly compare to alternatives or provide when-to-use vs. when-not-to-use guidance.

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