lists_get

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

With no annotations provided, the description must communicate whether the operation is safe. The verb 'Get' indicates a read-only action, but the description does not disclose additional behavioral aspects such as error handling for invalid list IDs, auth requirements, or the full scope of returned data beyond 'name and content'.

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 a single, front-loaded sentence that immediately states the action and resource. It avoids redundancy and is appropriately concise for the tool's simplicity.

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 tool is simple with one parameter, and the schema covers the parameter fully. The description conveys the purpose and hints at return content ('including its name and content'), which is adequate given the absence of an output schema and annotations. However, it could be slightly more explicit about the full return structure or common error scenarios.

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 schema fully documents the single parameter list_id with the description 'The ID of the list to get'. The tool description does not add new semantic detail about the parameter, so it remains at the baseline for high 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 the tool retrieves details for a specific ClickUp list, using the verb 'Get' with the resource 'list'. It distinguishes itself from sibling tools like lists_search and lists_list_in_space by specifying 'a specific' list, aligning with its input parameter list_id.

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 implies usage when a user needs details on a known, specific list, but it does not explicitly compare this tool with alternatives such as lists_search or lists_list_in_space. There is no when-not-to-use guidance, so the usage context is inferred rather than stated.

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