list_test_collections

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description does not need to repeat safe behaviors. It adds useful context by noting that results include execution stats, even if it does not elaborate on response shape or archived handling.

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 two sentences with no filler. The first sentence is the actionable purpose and the second provides conceptual context for what collections are used for, which is appropriately front-loaded.

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 read-only list tool with well-documented filters and pagination, this description is largely complete. It lacks explicit routing guidance against other list tools, and there is no output schema describing execution stat fields, but nothing blocks correct invocation.

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%, and every parameter already has a clear description. The tool description adds no additional parameter detail, but it does not need to; the baseline of 3 applies because the schema does the heavy lifting.

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 explicitly states the verb 'List', the resource 'test collections', and the scope 'in a project', and adds value with 'manual runs' and 'execution stats'. This distinguishes it from other list tools enough for an agent to identify the right resource.

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 when to use the tool by explaining collections organize manual test executions for sprints, releases, or ad-hoc testing. However, it does not explicitly name alternative tools like list_executions or list_test_cases, nor does it state when not to use them, leaving that routing to the agent's inference.

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