lemon-squeezy-mcp

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

No annotations are provided, so the description carries full burden. It states it 'gets details' but doesn't disclose behavioral traits like whether it's a read-only operation (implied but not confirmed), error handling (e.g., for invalid IDs), authentication needs, rate limits, or response format. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 that front-loads the core action ('Get details') and resource ('order item by ID'). There is zero wasted wording, and it directly communicates the essential information without redundancy or unnecessary elaboration.

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 annotations, no output schema, and a simple single-parameter input, the description is incomplete. It lacks details on behavioral aspects (e.g., read-only nature, error responses), return values (since no output schema exists), and usage context. For a tool in a server with many siblings, more guidance would help agents use it correctly.

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%, with the single parameter 'orderItemId' documented as 'The order item ID'. The description adds no additional meaning beyond this, such as format examples (e.g., numeric range) or context (e.g., where to find the ID). Given high schema coverage, the baseline score of 3 is appropriate, as the 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 'Get' and resource 'details of a specific order item by ID', making the purpose unambiguous. It distinguishes from siblings like 'list_order_items' (which returns multiple items) by specifying retrieval of a single item. However, it doesn't explicitly contrast with 'get_order' (which might retrieve the parent order), leaving slight room for improvement in sibling differentiation.

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. It doesn't mention prerequisites (e.g., needing a valid order item ID), exclusions (e.g., not for bulk retrieval), or comparisons to siblings like 'list_order_items' for multiple items or 'get_order' for parent order details. Usage is implied but not explicitly stated.

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