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 only the underlying REST endpoint as context and says nothing about pagination behavior, result ordering, or what happens if the connection has no estimates – modest added value beyond structured fields.

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, front-loaded with purpose and scope, zero filler. The endpoint mapping is arguably redundant but costs little.

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?

Adequate for a simple read-only list, but with no output schema the description could say what each estimate entry contains or note paginated results; those details are left entirely to inference.

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%, with page, per_page and hash_key all documented in the schema itself (including the note that hash_key is not the numeric id). The description only reflects hash_key via the URL template, so it adds nothing 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?

States a specific verb (List), resource (estimates), and a scoping constraint (of one connection/client) that separates it from the unfiltered hiveage_list_estimates. It does not name the sibling explicitly, so differentiation is implied by scope rather than spelled out.

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 scoping phrase implies when to use it (you have a connection and want its estimates), but there is no explicit when-to-use/when-not guidance and no reference to the sibling list_connection_invoices or list_estimates alternatives.

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