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

readOnlyHint=true already covers the safety profile, so the bar is lower, and the description clears it by disclosing the return envelope {count, results} and clarifying that count is the account total rather than the page size — a genuinely non-obvious behavior. It also maps to the underlying GET /v2/estimates endpoint. Rate limits or default page size are left to the 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?

Two tightly packed sentences: the first enumerates returned fields, the second covers the return envelope and the endpoint mapping. No filler, and the most decision-relevant content (what the tool returns) is front-loaded.

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 responsibly explains the return shape and disambiguates count as an account-wide total, which is exactly the kind of thing an agent would otherwise misread. What is missing is modest: no note on ordering, empty-result behavior, or default page size (though the schema covers the latter).

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 description coverage is 100%, so both 'from' and 'size' are already fully documented, including the pagination formula and the fact that this wrapper defaults to 25 rather than the API's 1000. The description adds nothing about either parameter, 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 description names a specific verb and resource ("List estimates") and enumerates the fields present in each record — number, status, line items, subtotal, tax, total, margin, e-sign state, related job/contact. That is far more informative than the title alone. Sibling differentiation is implicit via the resource name rather than stated (no contrast drawn with list_invoices or list_jobs), which keeps it from a 5.

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 or when-not-to-use guidance, and no alternative tool is named. The only usage signal is the resource name itself, which an agent would infer anyway. Nothing tells the agent how this differs from jobnimbus_list_invoices or when to prefer a get_* tool for a single record.

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