wopee-mcp

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

No annotations provided, but description fully compensates. Discloses idempotency ('Not idempotent'), specific side effects ('creates a suite and execution records'), rate limits ('10 seconds between dispatches'), retry behavior ('concurrent calls auto-retry with exponential backoff'), and return value ('Returns the created suite object'). Exceptional behavioral disclosure.

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?

Information-dense and well-structured: purpose → usage context → sibling alternative → parameters → side effects/idempotency → rate limits → return value. Slightly verbose but every sentence earns its place by conveying critical behavioral or usage information.

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?

Thorough coverage for a complex mutating tool. No output schema exists, but description explicitly states what returns ('created suite object'). Covers resource creation, platform state changes, timing constraints, and retry policies—sufficient for safe invocation.

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 has 100% coverage (baseline 3). Description adds semantic interpretation: maps additionalInstructions to 'free-text instructions' and additionalVariables to 'custom variables', 'starting URL', 'login credentials', and 'cookie preferences' (including specific enum-like values ACCEPT_ALL/DECLINE_ALL/IGNORE). This contextualizes how to populate the generic parameter structures despite schema being fully described.

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 action: 'Create a new analysis suite AND dispatch an AI crawling agent in one step.' Distinguishes from sibling wopee_create_blank_suite by contrasting auto-analysis vs manual population. Describes mechanism (real browser, navigation, discovery) precisely.

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?

Explicit when-to-use: 'Use this when you want to auto-analyze a web app.' Explicit alternative named: 'Use wopee_create_blank_suite instead if you want to manually populate the suite.' Clear guidance on choice between automation and manual workflows.

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