Fetch recent test executions

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

With no annotations, the description carries the full burden, and it does substantial work: it discloses the result shape (verdict PASSED/FAILED/INCOMPLETE, fallback execution status IN_QUEUE/IN_PROGRESS/FINISHED/FAILED/STOPPED) and explains the important semantic that INCOMPLETE is an infrastructure failure saying nothing about the application. It stops short of stating read-only safety, rate limits, or pagination beyond the 20-item cap.

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?

Front-loaded with the core action and scope in the first sentence, then usage routing, then return semantics. The verdict/status enumeration parenthetical is long and slightly run-on, but every element carries information the agent needs given there is no output schema.

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?

No output schema exists, so the description must explain returns, and it does so thoroughly (verdict, status fallback, agent reports). Combined with the env-var note and usage triggers, an agent has everything needed to call and interpret this tool 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?

Zero parameters, so the baseline is 4. The description adds useful context by stating 'Takes no input; uses WOPEE_PROJECT_UUID from environment', which documents an implicit configuration dependency an agent would otherwise have no way of knowing.

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?

Specific verb (Fetch) + resource (recent test case executions) with explicit scope ('up to 20, newest first') and project scoping. It is clearly distinguishable from siblings like wopee_fetch_executed_test_cases and wopee_fetch_analysis_suites because it states the recency window and the no-UUID-required angle.

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?

Gives explicit when-to-use triggers ('what's the status?', 'how did the tests go?') and the condition that selects it ('without needing to remember specific suite UUIDs' / 'don't have the specific suite UUID handy'). That directly routes the agent away from UUID-keyed siblings when no UUID is available.

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