create_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: the list persists for the session duration, items can be file paths, URLs, identifiers, or strings, and the workflow involves using the returned list_id with other tools. However, it doesn't mention potential errors, rate limits, or specific constraints beyond persistence.

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?

The description is well-structured with clear sections (purpose, usage, workflow, example) and front-loaded key information. It's appropriately sized, but the example section is somewhat detailed, which slightly reduces conciseness while adding clarity.

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?

Given no annotations, 100% schema coverage, no output schema, and moderate complexity, the description is mostly complete. It covers purpose, usage, workflow, and parameters well, but lacks details on error handling or output specifics (e.g., format of list_id), which would enhance completeness for a tool with no output schema.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds value by elaborating on the 'items' parameter semantics: it specifies that items can be 'file paths, URLs, identifiers, or any strings' and explains their purpose ('substituted into commands or prompts'), providing context beyond the schema's basic description.

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 the tool's purpose: 'Creates a named list of items for parallel processing.' It specifies the verb ('creates'), resource ('named list of items'), and distinguishes from siblings by focusing on creation rather than deletion, retrieval, or usage of lists.

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?

The description explicitly provides usage guidelines with a 'WHEN TO USE' section, listing specific scenarios like before running shell commands or AI agents across multiple items. It also references sibling tools (run_shell_across_list, run_agent_across_list) as alternatives for subsequent steps, clearly differentiating when to use this tool versus others.

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