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

Annotations already indicate read-only and idempotent behavior. The description adds that it returns raw data from Kiwify and supports bulk execution, but does not disclose potential side effects or authentication requirements beyond what is implied.

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 concise and structured with bullet points for actions. It front-loads the purpose and includes only necessary information. The '[Flattened action: get]' note adds slight confusion but does not significantly impact clarity.

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 the tool's 10 parameters and no output schema, the description covers main functionalities and most parameters. However, it omits explanation of the 'account' parameter and does not describe the output structure or pagination details beyond page_size and page.

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?

With 0% schema description coverage, the description compensates by explaining parameters for list (start_date, end_date, product_id, status, page_size, page) and get (sale_id), plus bulk support (sale_ids, product_ids). However, the 'account' parameter is not mentioned, and some format details are missing.

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 is for reading sales from Kiwify, listing two actions (list and get) with specific parameters. However, it does not explicitly differentiate from the sibling tool 'kiwify_sales_list', which may cause confusion.

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 list vs get (list for listing, get for single sale with sale_id), but does not provide explicit guidance on when not to use this tool or mention alternatives like kiwify_sales_list.

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