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

Annotations already mark the operation as read-only, idempotent, and non-destructive, so the bar is lower. The description adds valuable behavioral context beyond annotations: newest-first ordering, cursor pagination, optional case-insensitive filtering, deployment caveat, and the caller-identity constraint. It also discloses that each entry carries an encoded config usable by other tools.

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?

Three dense sentences with no filler. The core behavior is front-loaded, followed by the scoping caveat and the downstream compatibility note. Every sentence earns its place.

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 description is complete for a read-only list operation with an output schema available. It explains scope, ordering, pagination, filtering, deployment prerequisites, caller identification, and how the returned config can be used downstream. Nothing essential is missing.

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 coverage is 67% with q and cursor already described in the schema. The description reinforces q as a case-insensitive name filter and mentions cursor pagination, but does not add significant new meaning beyond the schema, especially for the 'limit' parameter which relies solely on its numeric constraints.

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 uses a specific verb ('Lists') with a clear resource ('tests registered to the signed-in account') and adds ordering and pagination details. It also distinguishes itself from siblings by noting that unlike other tools, the account scope cannot be expressed as an argument.

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?

It clearly states this tool only works on deployments with accounts and only for an identified caller, which sets the context for when it applies. It also mentions downstream tools that accept the returned config, implying a workflow, though it does not explicitly name alternatives or when-not-to-use conditions.

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