lemon-squeezy-mcp

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

With no annotations provided, the description carries full burden but only states it's a listing operation with optional filtering. It doesn't disclose whether this is paginated (though 'page' parameter hints at it), what permissions are needed, rate limits, response format, or whether it's safe/read-only. The description is minimal and leaves key behavioral traits unspecified.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes the key optional feature. Every word earns its place without redundancy or fluff.

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?

For a listing tool with no annotations and no output schema, the description is insufficient. It doesn't explain the response format, pagination behavior (though hinted by 'page' parameter), error conditions, or how filtering works. Given the context of sibling tools like 'get_webhook', more differentiation and usage context would be helpful.

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 description coverage is 100%, so the schema fully documents both parameters. The description adds marginal value by mentioning 'optionally filtered by store' which aligns with 'storeId', but doesn't provide additional context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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?

The description clearly states the verb ('List') and resource ('all webhooks'), and specifies optional filtering by store. It distinguishes this as a listing operation rather than creation or deletion. However, it doesn't explicitly differentiate from sibling 'get_webhook' (singular retrieval) or other list tools.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_webhook' (singular retrieval) or 'create_webhook'/'delete_webhook'/'update_webhook' (mutations). It mentions optional filtering but doesn't explain when filtering is appropriate or what happens without it.

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