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

readOnlyHint=true already declares the safe read profile, so the description's only added value is the underlying endpoint reference (GET /rinv/{hash_key}/invoices). It says nothing about result volume, whether the parent profile must exist, or any pagination behavior beyond what the schema covers.

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, purpose first, endpoint second. Efficient, though the raw API route is of marginal use to an agent and is the less valuable half.

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 read-only list with a fully documented 3-parameter schema and no output schema, the description is adequate but thin — it does not indicate what an invoice record contains or that an empty list is a valid outcome.

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% and hash_key is already documented as a short string rather than a numeric id, so the description adds no parameter meaning of its own. 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 the invoices a recurring invoice profile has generated'), which cleanly scopes it to one profile rather than all invoices. That implicitly separates it from hiveage_list_invoices and hiveage_list_connection_invoices, though neither sibling is named.

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?

Usage is only implied by the resource scoping; there is no explicit statement of when to prefer this over hiveage_list_invoices or hiveage_get_recurring_invoice, and no prerequisites or exclusions are given.

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