unitTestEvaluation

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

With no annotations, the description must disclose side effects, permissions, and output behavior, but it only says 'Evaluates unit test results'. This leaves the agent unaware of whether evaluation is read-only, requires prior test runs, or returns specific data.

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 short sentence, front-loaded and without waste. While it is terse, it achieves conciseness and avoids unnecessary detail, though a bit more context would improve it.

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?

Given the minimal description, lack of output schema, and no annotations, the tool omits critical context about evaluation outcomes, usage scenarios, and any dependencies. This is insufficient for an agent to confidently invoke it correctly.

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 input schema covers 100% of parameters with descriptions ('clas' and 'flags'), so the description adds no extra semantics beyond what the schema already provides. Baseline 3 applies since the schema does the heavy lifting for parameter understanding.

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 states a verb and resource ('Evaluates unit test results') but lacks specificity about what evaluation entails. It does not differentiate from sibling tools like unitTestRun or unitTestOccurrenceMarkers, leaving ambiguity about its unique function.

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 is provided on when to use this tool versus alternatives. The description gives no context for prerequisites, exclusions, or typical scenarios, leaving the agent without direction.

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