wopee-mcp

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

No annotations provided, so description carries full burden. Discloses 'Returns the artifact content as text', 'returns an empty result' for missing artifacts, and validation failure behavior ('omitting it returns an error'). Explicitly declares read-only nature compensating for missing safety annotations.

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?

Five sentences each earning their place: (1) Core operation, (2) Return format, (3) Usage context with siblings, (4) Safety declaration, (5) Parameter validation rules & edge cases. Front-loaded with purpose, no redundancy.

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 no output schema, description adequately covers return values ('text', 'empty result'), parameter interdependencies (type/identifier coupling), sibling workflows, and read-only safety. Sufficient for a 3-parameter fetch tool with conditional validation logic.

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% with detailed descriptions (baseline 3). Description adds value by clarifying runtime behavior: identifier causes an error if omitted for PLAYWRIGHT_CODE, and is explicitly 'ignored' for other types—nuances beyond the schema's static 'Required only when' declaration. Adds concrete example 'US004:TC006'.

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?

States specific verb 'Retrieve' + resource 'test artifact' + scope 'from a suite'. Explicitly references siblings 'wopee_generate_artifact' and 'wopee_update_artifact', clearly positioning this as the read counterpart to those mutating operations.

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 when-to-use guidance: 'Use this to review what wopee_generate_artifact created, or to retrieve existing artifacts before editing with wopee_update_artifact.' Also explicitly states read-only safety with 'Does NOT modify any data'.

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