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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real value by documenting the return envelope ('{ meta, response }'), which matters since there is no output schema, but it says nothing about pagination iteration, result-set size limits, or rate limiting.

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 very short, front-loaded sentences with no filler; the core purpose leads and the technical details follow. The endpoint sentence ('Accelo API: GET /api/v0/invoices') is borderline redundant with the tool name but does document the upstream call.

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 tool with fully documented parameters, the description covers purpose, underlying endpoint, available query modifiers, and the response envelope, which compensates for the absent output schema. Only the mechanics of iterating pages and any result limits are left unaddressed.

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 five parameters are already documented in detail in the schema. The description only restates the parameter names ('_page/_limit/_fields/_filters/_search') without adding semantics beyond what the schema provides, which is the baseline 3 case.

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 opens with a specific verb+resource pair ('List invoices') and names the underlying endpoint, so the operation is unambiguous. It does not explicitly differentiate itself from the sibling get_invoice (single-record retrieval) or from the many other list_* tools, so an agent must infer the plural scope from the name alone.

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 when-to-use guidance, no condition selecting this over get_invoice, and no mention of prerequisites such as auth or required scopes. The supported query-parameter list hints at browsing/filtering, but that inference is left entirely to the reader.

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