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

With readOnlyHint=true already covering safety, the description adds real value: it discloses the payload shape ('items, payments and amounts due/paid') and a pagination constraint ('Max 100 per page'). Auth requirements and whether the last-updated filters differ in semantics from issue-date filters remain unstated.

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 tight sentences, front-loaded with filters, then payload, then pagination. The trailing 'IntakeQ: GET /invoices.' endpoint reference is low-value padding for an agent but not harmful.

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?

No output schema exists, so the description usefully summarizes the return payload and page cap. All parameters are covered by the schema, and no required params exist. It stops short of stating pagination termination or total-count behavior, but the essentials for a correct call are present.

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 all 8 parameters are already documented with types, patterns and enum values. The description only echoes the same filter dimensions (client, issue date range, status, practitioner, last-updated range) without adding syntax or interaction guidance, 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?

Starts with a specific verb ('Query') on a specific resource ('invoices') and enumerates the filterable dimensions plus what each record contains. It reads clearly as a bulk-list operation, distinct from the singular intakeq_get_invoice, though it never names that sibling explicitly.

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 implied by the filter list (client, date range, status, practitioner, last-updated) but there is no explicit statement of when to use this versus intakeq_get_invoice or when to combine filters. 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.