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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral context beyond that: the return shape {count, results} and the key semantic that 'count is the account total' rather than the page size, plus the underlying endpoint (GET /v2/estimates).

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?

Two tight sentences with zero filler: the resource and returned fields come first, then the response envelope and endpoint. Every clause carries information.

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 correctly takes on the return-shape burden, naming the envelope and clarifying that count is the account-wide total (important for pagination reasoning). Pagination mechanics live in the schema, so nothing critical is missing, though a note on default page size or ordering would round it out.

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% and both parameters (from, size) are thoroughly documented in the schema, including offset math and the 25-vs-1000 default discrepancy, so the description need not compensate. The description adds no parameter detail at all, making the baseline 3 correct.

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?

Specific verb ('List') plus resource ('estimates'), with an enumeration of the returned fields and the response envelope. The resource name alone cleanly separates it from siblings like jobnimbus_list_invoices and jobnimbus_list_jobs.

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?

There is no when-to-use guidance, no mention of alternatives (e.g., get-invoice-style retrieval or filtered search), and no stated prerequisites. The agent can infer it lists estimates, but nothing tells it when this is the right choice over another list/get tool.

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