list_lists

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

The tool name and description imply a read-only listing operation. No annotations are provided, so the description carries the full burden. While it doesn't explicitly state behavior (e.g., no side effects), the simple nature and examples make it clear enough. A score of 4 is appropriate as it adds value beyond the name.

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, no wasted words. The information is front-loaded, concise, and every sentence serves a purpose.

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 parameters and an output schema, the description is complete. It covers what the tool does, provides examples, and directs to related tools. No additional context needed.

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 no parameters, so baseline is 4. The description adds value by giving examples of the lists' content, which helps the agent understand what to expect.

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 lists controlled-vocabulary lists for the project, with specific examples like welders and materials. It also distinguishes itself from the sibling 'list_list_items' by directing the agent to use that tool to read one list.

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 guides when to use this tool (to list all controlled-vocabulary lists) and when to use the alternative 'list_list_items' (to read one specific list). Provides clear context for tool selection.

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