testpass_run

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

Discloses idempotency via task_id, duplicate detection (was_duplicate), and retry safety. With no annotations, this provides valuable behavioral context beyond the schema.

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?

Concise three-sentence paragraph that efficiently conveys purpose, behavior, and key parameter details. No unnecessary words, though a structured bullet list might improve scanning.

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?

Covers inputs, behavior, and output (run_id, verdict summary, was_duplicate) adequately. Without output schema or annotations, the description fills the gaps reasonably well.

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?

Adds significant meaning beyond the input schema, especially for task_id: explains its purpose, recommended generation method, and consequences of omission. Other parameters are also well-contextualized.

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 starts a TestPass run against an MCP server, seeds checks, and returns run ID and initial verdict. It distinguishes from sibling tools like testpass_status and testpass_edit_item.

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?

No guidance on when to use this tool versus alternatives (e.g., testpass_status, testpass_report_html) or when not to use it. Missing context for appropriate usage scenarios.

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