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

The readOnlyHint annotation already establishes this as a safe read, so the bar is lower. The description adds worthwhile context by listing the returned fields (status, due date, amount due, payer, receipt URL) and the upstream endpoint, but says nothing about pagination behavior despite page/page_size parameters.

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?

One dense sentence plus an endpoint reference, front-loaded on the resource and returned data. No filler, though the field enumeration is slightly list-heavy for a tool whose return shape could be inferred.

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?

There is no output schema, so the description's field listing usefully covers what comes back, and all seven optional params are covered by the schema. Missing only pagination guidance and an explicit pointer to the single-invoice sibling.

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 every parameter is already documented in the schema. The description only echoes the status values (with a truncated list versus the schema's full enum) and the membership filter, adding no syntax or format detail beyond 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?

States a specific verb+resource ('List invoices') and enumerates the returned fields and supported filters, which is more than a restatement of the name. It implies but never explicitly says how it differs from the singular goteamup_get_invoice sibling, so it stops short of full sibling differentiation.

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 description tells the agent the two filter dimensions (status, customer membership), which implies when the tool is useful, but offers no when-not conditions, prerequisites, or named alternative such as get_invoice for a single record.

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