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

The description adds a temporal behavioral trait by specifying 'recent,' which guides the agent on the scope and freshness of the data being retrieved. Since there are no annotations, the description carries the full burden of providing this necessary context.

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 maximally concise, providing all necessary context in one direct and efficient sentence without any superfluous language.

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 parameter-less list tool, the definition is adequate. It clearly identifies the resource ('prompt tests') and the scope ('recent') without needing to detail the output format, which is generally left to the output schema or execution environment.

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?

With zero parameters and 100% schema coverage, the schema handles all structural definition. The description provides no semantic meaning beyond defining the resource itself, adhering to the baseline score for parameter-less tools.

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 resource being accessed ('prompt tests') and the action ('list'), distinguishing it from singular retrieval tools like 'get_test' by implying a collection of items.

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 usage is implied by the function name and resource description, but there are no explicit instructions on when to use this list function versus other potential list functions from the sibling set.

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