manage_lists

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the feature is account-gated and requires a probing 'list' call to detect availability. It stops short of describing deletion consequences or permission needs, but it meaningfully exceeds 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?

Front-loaded with purpose, then a compact action table where each line earns its place, then minimal examples. Slightly long overall but no filler; the action list is the core content an agent needs for a multiplexed tool.

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?

For a seven-action multiplexed tool with no output schema, the description documents every action's requirements and provides worked examples covering read, create, and mutation paths. Combined with full schema coverage and annotations, an agent has everything needed to invoke it 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 description coverage is 100%, so baseline is 3. The description goes further by mapping each action to its required inputs (get/create/edit need name or id; add_chat needs conversation_id), which the flat schema cannot express. It doesn't clarify the single-vs-array conversation_id semantics beyond the schema, keeping it below 5.

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?

States a specific verb+resource (manage personal chat lists) and distinguishes it precisely from the sibling manage_labels by calling it the personal-account equivalent of Business labels. An agent can tell what this tool does and how it differs without opening the schema.

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?

Gives clear context (organizing chats into categories) and a concrete prerequisite: 'Not available on all accounts — check with action "list" first.' Each action's use is implied by its requirement list, but there is no explicit when-not-to-use guidance beyond the labeling distinction.

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