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

Annotations already declare readOnly/destructive/openWorld, so safety is covered. The description adds real operational context beyond them: a page cap of 100 items, the cursor-based pagination loop, and an auth requirement (Cotlet API key with access to this app).

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?

Five short sentences, front-loaded with what the resource is and why to call it, then pagination and auth details. No filler or repetition.

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 read-only list tool whose annotations already cover the safety profile, the description supplies everything needed: purpose, search semantics, pagination contract, field coverage, and the credential requirement. No output schema is needed since return fields are named.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: search matches part of the item code OR name, pages cap at 100 items (schema only says default 20), and the returned cursor is fed back as the cursor parameter.

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?

States a specific verb (Lists) and resource (Item records) and enumerates what an item carries (code, name, group, unit). It is clearly distinguishable from siblings like erpnext_list_customers or erpnext_get_stock_balance.

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?

Gives a concrete reason to call it (to get the exact item code to place on an invoice line) and describes the search matching behavior. It does not name an alternative tool or state when NOT to use it, but the intended context is unambiguous.

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