wopee-mcp

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

No annotations provided, so description carries full disclosure burden. Effectively reveals: async behavior ('returns confirmation that generation started' implying background processing), destructive potential ('overwrites the previous version'), and quality constraints (order dependency affects output quality). Missing only minor details like rate limits or exact error states.

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?

Perfectly structured and front-loaded. Every sentence earns its place: purpose first, usage pattern (multiple calls), ordering constraints, success behavior, sibling references, and overwrite warning. No redundancy or filler despite covering complex workflow dependencies.

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?

Excellent coverage for a generation tool without output schema. Explains return value ('confirmation that generation started'), side effects (overwrite behavior), and full workflow integration (fetch_artifact for retrieval). Only minor gap is lack of error state descriptions or timing estimates for generation completion.

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?

Schema coverage is 100% so baseline applies. Description loosely references the type parameter ('Each call creates one artifact type') but adds no syntax, format, or constraint details beyond what the schema already documents for the 'type' and 'suiteUuid' parameters.

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?

Excellent specificity: 'Generate AI-powered test artifacts' provides clear verb and resource. Explicitly distinguishes from siblings by stating 'Do NOT use this to update existing artifacts — use wopee_update_artifact instead' and directing users to 'wopee_fetch_artifact' for retrieval, clearly delineating the create/update/read separation in the tool suite.

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?

Outstanding guidance: explicitly states when-not to use ('Do NOT use this to update'), names the correct alternative ('use wopee_update_artifact instead'), and details critical workflow dependencies ('APP_CONTEXT must be generated before user stories, and user stories before test cases'). Also specifies the async retrieval pattern requiring wopee_fetch_artifact.

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