List Test Suites

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

The readOnlyHint annotation correctly indicates a read-only operation, and the description reinforces a non-mutating action. It also transparently notes the dependency on a previously set project context, which will cause failure if absent.

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 concise sentences with no redundancy. It front-loads the main action and then adds the prerequisite, making it easy to parse quickly.

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 simple list operation, the description covers the essential context: the scope (active project), the prerequisite (set_context), and the output highlights (stats). It does not describe response formatting, but skip/take parameters imply standard pagination, and no output schema exists to demand further detail.

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 two parameters (skip and take) have complete schema coverage with descriptions, defaults, and maximums. The tool description does not add extra semantic detail beyond the schema, but none is needed since the parameters are self-explanatory.

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 operation ('List test suites'), the resource ('test suites'), and the scope ('in the active project'). It also mentions the returned statistics and the prerequisite, making the purpose unmistakable.

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 states the precondition ('Requires project context') and instructs to call set_context first, which is key usage guidance. It does not enumerate alternative tools, but the instruction is sufficient for correct invocation.

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