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

readOnlyHint=true already declares the safe-read profile, so the bar is lower. The description adds only the underlying HTTP route, which does not tell the agent anything about pagination behavior, ordering, or what a returned profile contains; it is neutral rather than contradictory.

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 purpose front-loaded; the API route in the second sentence is mild filler but does no harm. No redundancy beyond the restated title.

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?

A read-only paginated list tool with no output schema, so the description should ideally say something about the returned shape or pagination semantics. The parameter schema covers the inputs, but the description is silent on output and on how pages relate to results.

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 all three parameters (hash_key, page, per_page) are documented in the schema, including the hash_key-vs-numeric-id distinction and the enum-like per_page values. The description adds nothing beyond that, so 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 (List) and resource (recurring invoice profiles) plus the scoping qualifier 'of one connection (client)', which distinguishes it from hiveage_list_recurring_invoices and hiveage_get_recurring_invoice. It stops short of naming those siblings explicitly, so it is clear but not fully disambiguating by name.

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 scope phrase 'of one connection' implies the use case (recurring invoices belonging to a given client), but there is no explicit when-to-use, when-not, or named alternative such as the global list or the single-get tool. The agent must infer the routing decision.

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