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

With no annotations, the description carries the full burden of behavioral disclosure, yet it only states what data is present. It does not clarify that this is a read-only operation, whether results are paginated or sorted, or what the default status scope is when no filter is supplied.

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?

The description is a single compact sentence with no wasted wording, and the resource and returned fields are front-loaded. However, the fragmentary phrasing omits an explicit action, which slightly reduces clarity.

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 one-parameter list tool, the description covers the resource and some returned fields well enough to be usable. It still leaves out important context for an agent, including whether this is read-only, how results are ordered or paginated, and what fields besides status and amount are returned.

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?

The schema already says the status parameter is an optional filter, and the description adds useful meaning by naming the concrete status values: draft, sent, overdue, and paid. This gives the agent concrete filter values that are not encoded as an enum in 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?

The description clearly identifies the resource as "The firm's invoices" and indicates the fields returned: status values and amounts. The listing verb is only implied by the tool name, not stated in the description, but the resource is easy to distinguish from siblings like chase_invoice and send_invoice.

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?

There is no guidance on when to use this tool versus alternatives such as chase_invoice or send_invoice, and no mention of scope or preconditions. The name makes the basic intent obvious, but the description itself offers no usage direction.

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