lead_labels_delete

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

No annotations are provided, so the description carries the full burden. It discloses the key behavioral consequence: 'Existing leads carrying this label will lose it after deletion.' However, it does not mention authorization requirements, error behavior (e.g., if label doesn't exist), or reversibility, which would be helpful for a delete operation.

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 extremely concise with two sentences. The first states the action, and the second explains the consequence. Every word is necessary; no redundancy or extraneous information.

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 simple delete operation with one parameter and no output schema or annotations, the description covers the main action and a critical side effect. It could be improved by mentioning possible error conditions or permission needs, but it is largely complete for its complexity.

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 input schema has 100% description coverage with the parameter 'id' described as 'Lead label UUID'. The tool description adds no additional meaning beyond the schema, just restating 'by UUID'. Baseline score of 3 is appropriate.

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: 'Delete a lead label by UUID.' It identifies the specific resource (lead label) and the identifier (UUID). It also distinguishes from sibling tools like lead_labels_create and lead_labels_update by explicitly being the delete operation.

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 implies that the tool should be used when you want to delete a lead label, but it does not provide explicit guidance on when not to use it or prerequisites (e.g., required permissions). It mentions the side effect on leads but lacks context about alternatives or conditions for safe use.

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