wopee-mcp

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

No annotations provided, so description carries full burden. Excellently discloses: safety profile ('Read-only'), external dependency ('uses WOPEE_PROJECT_UUID from environment'), return structure ('array of suite objects with UUIDs, names, types...'), empty state behavior ('Returns an empty array'), and failure condition ('Fails if WOPEE_PROJECT_UUID is not configured').

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?

Four dense sentences covering purpose, return values, usage guidelines, and operational constraints. No redundant words. Front-loaded with the core action ('List all analysis suites'), followed by return details, usage context, and finally technical constraints.

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?

Despite no output schema and no annotations, description fully compensates by detailing the return object structure (UUIDs, names, types, statuses), enumerating specific enum values (ANALYSIS, AGENT, IDLE, IN_PROGRESS, FINISHED), and covering edge cases (empty array, missing env var). Complete for a zero-parameter discovery tool.

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 (baseline 4). Description adds essential context that the tool 'Takes no input; uses WOPEE_PROJECT_UUID from environment,' explaining the implicit configuration dependency not captured in the empty input schema.

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?

Clear specific verb ('List') and resource ('analysis suites'). Explicitly distinguishes from sibling tools by stating it discovers suites needed for wopee_generate_artifact, wopee_fetch_artifact, wopee_update_artifact, and wopee_dispatch_agent, establishing its role as a prerequisite discovery tool.

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?

Explicitly states when to use ('discover existing suites before calling other tools') and names four specific sibling tools that require the UUIDs returned by this tool. Also clarifies what it does NOT do ('does not create or modify anything'), distinguishing it from wopee_create_blank_suite.

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