labels_delete_category

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

The description mentions 'delete,' implying a destructive action, but it discloses no behavioral traits beyond that. There are no annotations to supplement, so the description should explain consequences (e.g., cascading effects on associated labels), but it does not.

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 sentence and concise. However, it includes a technical reference to a WebSocket endpoint that may not be essential for an agent to understand the tool's purpose.

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?

Given the tool has two required parameters and no annotations, the description is too minimal. It does not cover typical context like error handling, success indicators, or prerequisites. The existence of an output schema is noted but not leveraged in the description.

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?

Both parameters (scope, category_id) are required but lack descriptions in the schema (0% coverage). The description does not explain what these parameters mean or how to use them, providing no added value over the bare schema.

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 it deletes a category, distinguishing it from sibling tools like labels_delete_label or labels_create_category. However, it lacks specificity about what type of category, but the inline code reference to the WebSocket endpoint adds a specificity that an agent might not need.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., when to delete a category vs. a label). No context about prerequisites or conditions is given.

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