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

readOnlyHint=true already tells the agent this is a safe read. The description adds that results are date-sorted and maps to GET /estm, which is modest extra context. It says nothing about whether results are paginated envelopes, how many records come back, or whether draft/sent statuses are all included.

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 short sentences with the resource stated first and the endpoint mapping last. Nothing is padded, though the raw endpoint reference contributes little for an agent that already reads structured fields.

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 simple, fully-documented read-only list tool with no output schema, the description supplies the essential scope (all estimates, date-ordered). Only the relationship to the connection-scoped variant is missing, which is a minor gap at this complexity level.

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 page, order, and per_page are all fully documented with defaults and enum values. The description's 'sorted by date' hints at the sort key but adds no syntax or constraint detail beyond the schema; 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?

States a specific verb and resource ('List estimates (quotes)') plus the underlying endpoint, so the operation is unambiguous. It does not distinguish itself from the sibling hiveage_list_connection_estimates, which is the one nearby tool an agent could confuse it with.

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?

Listing all estimates is implied by the absence of any filter parameters, but the description never states when to prefer this over hiveage_list_connection_estimates or hiveage_get_estimate. Usage must be inferred from the schema being filter-free.

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