create_label

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

Annotations already indicate read/write nature (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds 'external write' context beyond annotations, but lacks details on error handling, duplicate behavior, or side effects.

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?

Two sentences, front-loaded with core purpose, no unnecessary words. Every sentence adds value.

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 essential context (Gmail, exact name, external write, scope). Output schema handles return values. Missing error conditions or duplicate handling, but acceptable for a simple creation 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?

Schema description coverage is 33% (only 'name' described). Description adds no additional meaning for 'label_list_visibility' or 'message_list_visibility' parameters, failing to compensate for low coverage.

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 verb (create), resource (Gmail user label), and scope (exact name, external write, does not apply to messages). Clearly distinguishes from siblings (delete_label, update_label, send_email).

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 states what the tool does and does not do (does not apply label to messages). Provides clear context for when to use, but no explicit when-not-to or alternatives mentioned.

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