lemon-squeezy-mcp

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: conditional logic (check existence first), creation with specific source ('AI Agent'), and return value (Lead ID). However, it doesn't mention mutation implications, error handling, authentication needs, or rate limits for a write operation.

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 perfectly concise at two sentences with zero waste. It's front-loaded with the core purpose, followed by behavioral details. Every word earns its place in explaining the tool's conditional logic and return value.

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 mutation tool with no annotations and no output schema, the description provides adequate but incomplete context. It explains the conditional write behavior and return value, but lacks details about error cases, side effects, or what happens when a Lead already exists (does it update or skip?).

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 already documents all 5 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline of 3 is appropriate when 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 tool's purpose with specific verbs ('sync', 'checks', 'creates') and resources ('customer', 'Salesforce CRM', 'Lead'). It distinguishes from sibling tools like 'create_customer' by specifying the CRM integration aspect and conditional logic (check existence before creation).

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 implies when to use this tool (for syncing customers to Salesforce CRM) but doesn't explicitly state when NOT to use it or name alternatives. It doesn't mention prerequisites like CRM connectivity or compare with other customer-related tools like 'create_customer' or 'update_customer'.

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