delete_label

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

Discloses permanent deletion and impact on messages. However, without annotations, could explicitly state irreversibility and safety considerations.

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?

Extremely concise with one sentence plus a scope note. Every word adds value; front-loaded with primary action.

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?

Covers purpose, scope, and side effect. Lacks output description and error handling, but sufficient for a simple deletion tool.

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?

No additional meaning beyond schema; label_id is undocumented in both schema and description. Does not leverage list_labels for obtaining IDs.

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?

Clearly states the verb (delete), resource (user label), and a key effect (messages keep other labels). Distinguishes from siblings like update_label and trash_thread.

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?

Explicitly mentions required scope (gmail.modify) but does not guide when to use this tool vs. alternatives like update_label, nor prerequisites (label existence).

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