Create a folder or label

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and idempotentHint=true. The description adds behavioral context by noting 'it changes your folder and label structure' and the need for confirmation. This goes beyond annotations, though it doesn't detail edge cases like idempotency behavior.

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 the main purpose, then the gating instruction. No wasted words, well-structured.

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?

The description covers the essential purpose and gating requirement. It omits explicit mention of dry_run in the text, but the schema covers that. For a simple creation tool with no output schema, this is sufficiently complete for an agent to use correctly.

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 has descriptions for name and dry_run, but kind and confirmed lack descriptions. The description adds meaning for 'confirmed' by requiring confirmed=true after user confirmation, and clarifies that 'name' and 'type' (kind) must be verified. This compensates for the 50% schema 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?

The description clearly states 'Create a new label or folder' which is a specific verb+resource, and the sibling list shows other create actions like create_draft, so it distinguishes itself. It also mentions the gated nature, adding clarity.

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 the gating condition: 'confirm the exact name and type with the user, then call with confirmed=true.' This tells the agent when to use it and what prerequisite steps are needed, including the confirmation requirement. It also implies dry_run can be used without confirmation.

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