Delete a label

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

Annotations already set destructiveHint: true, so the description should disclose additional behavioral traits beyond that. The description only restates the HTTP method and authorization, adding no new information about side effects, irreversibility, or data impacts. This is a missed opportunity to supplement the annotations.

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 only two sentences, but it lacks necessary detail. While it is front-loaded with the purpose, the brevity results in under-specification. The structure is minimal but efficient, though not optimally informative.

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 that there is an output schema, the description does not need to explain return values. However, for a destructive operation, more context is needed: what happens to associated resources, whether the operation is reversible, or any constraints. The description fails to provide a complete picture for safe invocation.

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?

With schema coverage at 50%, the description should clarify the parameters. However, it does not explain the 'labelId' or 'body' parameters beyond what the schema already provides. The description adds no value to the agent's understanding of how to use these parameters.

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 'Delete a label', which is a specific verb and resource. The tool name 'pc_delete_labels_by_label_id' aligns with this purpose, and among sibling tools like 'pc_get_companies_by_company_id_labels' and 'pc_post_companies_by_company_id_labels', it is distinct as 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 provides no explicit guidance on when to use this tool vs alternatives. It mentions the HTTP method and authorization class but does not specify prerequisites, such as needing an existing label ID, or contraindications. Without this, the agent lacks context for proper invocation.

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