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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful mutation context ('Cotlet does not create or edit them') and an auth prerequisite (Cotlet API key with access), but says nothing about pagination, ordering, or result limits for a list endpoint. With annotations carrying safety, a 3 is appropriate.

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?

Three short sentences, front-loaded with purpose, then the drill-down pointer, then the read-only/auth note. No filler, but the opening 'AccuLynx: Estimates on a job with name, total and date' is a fragment that restates the title a bit.

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 single-param read-only list, the description covers purpose, sibling routing, mutability, and auth. It omits pagination/ordering behavior for the returned list and there is no output schema, so an agent cannot tell how many estimates come back or in what order.

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 the single parameter's description ('Job ID from list_jobs') already documents it, so the baseline is 3. The description mentions the job-scoping and the estimate_id handoff, which adds marginal value but no new syntax or format details beyond the schema.

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) and resource (estimates on a job), plus the returned fields (name, total, date). It distinguishes itself from get_estimate by naming that sibling as the drill-down path, but the per-job scoping is implied rather than compared against any hypothetical job-less variant.

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?

Explicitly routes the agent: 'Pass estimate_id to get_estimate for the sections and line items.' It declares the estimates are read-only and what credential is required. Missing only an explicit statement of when not to use it (e.g., if you already have the estimate_id, call get_estimate directly).

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