lupa_list_tests

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

No annotations provided. Description clarifies it's a read-only operation ('without running them'), but fails to mention any other behavioral traits like side effects, auth needs, or output format.

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?

Single sentence with 15 words, no redundancy. Every part is essential.

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?

No output schema exists; description does not mention return format. However, the tool is simple and the context is adequate for a listing operation. Some may expect details on output structure.

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?

Input schema provides 100% description coverage for parameters. The description adds the filtering context ('Optionally filter the list'), but does not enhance parameter meaning beyond what schema already provides.

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 test files, suites, and tests without running them, distinguishing it from lupa_run_tests. The verb 'list' and resource 'test files, suites, and tests' are specific.

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?

Implies when to use (list instead of run) via 'without running them'. Does not explicitly state when not to use or compare to sibling tools, but the purpose is clear.

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