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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful context (results are ordered by recency and scoped to the selected business) but says nothing about default page size, limits, or whether the 'query' parameter is free-text search.

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 the core action, and no filler. Some of the limited space is spent on the vague phrase 'the business you picked' instead of the undocumented limit/query parameters.

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 simple four-parameter read tool with no required params and no output schema, so return-value explanation is not needed. However, ordering, default result count, and the purpose of the query and limit parameters are all unstated, which leaves meaningful gaps for an agent to guess at.

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 0%, so the description must carry the parameter burden, yet it only loosely maps 'status' and 'customer' to the status and clientId parameters. The limit and query parameters are never explained, leaving half the parameters undocumented in both schema and description.

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 concrete verb+resource ('See the newest invoices') and adds scope ('for the business you picked'), which lets an agent distinguish it from get_invoice or the create_* siblings. It does not explicitly distinguish itself from list_overdue_invoices/list_unpaid_invoices, which are the closest alternatives.

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: the tool lists the newest invoices, so it is the general listing entry point versus the filtered list_overdue_invoices/list_unpaid_invoices siblings. No when-to-use, when-not-to-use, or alternative is named, so the agent must infer routing from the sibling names.

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