wopee-mcp

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

With no annotations provided, description carries full burden and discloses 'Read-only: does not trigger any execution', explains return behavior ('Returns an empty array if no test cases have been executed'), and documents the polling pattern for async operations.

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?

Well-structured with purpose front-loaded, workflow guidance in the middle, and exclusions at the end. Every sentence provides unique value—no repetition of schema details or tautology.

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?

Compensates effectively for missing output schema by detailing return structure (status values IN_PROGRESS/FINISHED/FAILED, agent report, code report) and edge cases (empty array), providing complete workflow context.

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?

Despite 100% schema coverage, description adds valuable context: example analysis identifier format ('A068') and discovery guidance ('found in suite data'), reinforcing where to obtain this optional parameter.

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?

Description opens with specific verb 'Retrieve' and clear resource 'results of test cases executed by the autonomous agent'. It distinguishes from sibling wopee_fetch_artifact by explicitly stating this is for execution results, not artifacts like user stories or code.

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?

Provides explicit sequencing ('Use this after wopee_dispatch_agent'), polling instructions ('if status is IN_PROGRESS, wait and call again'), and clear alternative tool reference ('Do NOT use this... use wopee_fetch_artifact for that').

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