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

Annotations already declare read-only, idempotent, closed-world behavior, and the description still adds non-obvious traits: pagination is one page per call, tax rates appear only on the first page and are empty on later pages, and an empty page terminates the list. Those are behavioral facts not derivable from annotations or schema.

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?

Dense but front-loaded: payload, then pagination, then tax-rate caveat, then cursor mechanics. The opening two clauses partially overlap ('Saved items from your Items list' / 'Lists the items you saved in Joist'), which is the only real redundancy.

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?

With no output schema, the description carries the burden of describing returns, and it does: items with name, rate, description, item_id, plus tax_id usable in create_estimate/create_invoice. Pagination termination is also covered, so nothing an agent needs to call this correctly is missing.

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 cursor and search are already documented in the schema, and the description largely restates them ('Pass next_cursor back as cursor'). It adds only marginal meaning, such as search being a name match on the item name, so the baseline 3 fits.

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?

Names a specific verb and resource (list saved items from the Joist Items list) and adds the distinctive extra payload (tax rates on page one). An agent can distinguish it from siblings like list_clients or list_estimates without opening any schema.

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 clear conditions: use it to fetch saved items and reuse their names/rates as line items rather than guessing prices, and search mode uses the name match. It states no explicit exclusions or named siblings to prefer instead, so it stops short of full when/when-not guidance.

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