create_label

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

No annotations provided, so description carries full burden. Discloses nesting behavior, return shape, and auth scope. Does not clarify behavior if label already exists or effects on existing messages.

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 providing key information without extraneous detail. Efficient but could be slightly more structured with separate lines for prerequisites vs return.

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 basic creation, nesting, return, and auth scope. Missing details on error handling, uniqueness constraints, and the two optional enum parameters' effects. Adequate but not comprehensive.

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?

Only 25% schema description coverage; description adds nesting info for 'name' but does not explain 'label_list_visibility' and 'message_list_visibility' enum options. Incomplete parameter documentation.

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 'Create a user label', specifies nesting using '/', and mentions return value '{id, name}'. Distinguishes from sibling tools like update_label by focusing on creation.

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?

Mentions required scope 'gmail.modify' but does not provide guidance on when to use this tool versus alternatives like update_label or delete_label. No explicit when-not or context.

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