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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds genuine extra context: ordering ('newest first'), page capacity ('up to 100'), and an auth prerequisite ('Needs the user's Cotlet API key with access to this app'). It stops short of total counts or rate-limit behavior, but this is solid added value.

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 short and mostly front-loaded, but the first sentence ('Estimates with client, total, status and the date they were sent') is largely redundant with the second sentence's field enumeration. That duplication wastes a sentence in an otherwise compact definition.

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 return values, and it does list the returned fields (client, total, status, date sent) plus ordering and page size. Auth requirement is also noted. Only minor gaps (no guidance on pagination continuation or totals) keep it from a 5.

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 all three parameters (limit, since, status) are already documented in the schema with enum values and defaults. The description only restates the status filter and the 100-per-page cap, adding almost nothing beyond structured data, so the baseline 3 applies.

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 second sentence ('Returns estimates, newest first, with client, total, status and the date sent') states the resource and operation clearly, and the read-only listing nature distinguishes it from workiz_create_estimate / workiz_send_estimate. It never explicitly names a competing sibling, though, and the first sentence reads more like a field list than a purpose statement.

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 line 'Filter by status to find the ones still waiting for an answer' implies a usage scenario, and filtering guidance is present. However, there is no explicit when-to-use vs. when-not, nor any routing to an alternative (e.g., vs. workiz_list_invoices), leaving selection guidance implicit.

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