cypress_get_last_run

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

No annotations are provided, so the description carries the burden. It discloses the output content (full structured results, runId, args, test details) and the verb 'Return' suggests a read-only operation. However, it does not specify behavior when no previous run exists, potential errors, or any side effects, leaving some ambiguity.

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 a single, efficient sentence that front-loads the main action ('Return') and packs in key details (full structured results, most recent run, runId, args, test details). No wasted words.

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 0-parameter getter with no output schema, the description covers the essential return value details. It lacks explicit error/empty-run behavior, but the overall context is clear enough for an agent to invoke the tool confidently.

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 tool has zero parameters, and the input schema is empty. The description does not need to explain parameters, and it does not add parameter-specific meaning. Baseline for 0 params is 4, and the description correctly indicates the tool takes no input while describing the output.

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 returns 'the full structured results of the most recent Cypress test run' with specific contents (runId, args, all test details). This is a specific verb + resource, and it distinguishes from siblings like cypress_rerun_last (which reruns) and cypress_get_failure_context (which gets failure context only).

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 usage: fetch results of the most recent run. However, it does not explicitly mention when to use this tool over alternatives, nor any scope limitations or exclusions. The agent can infer when to use it from the purpose, but there is no direct guidance.

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