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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the description's job is lighter. The description adds the returned field set, but says nothing about pagination defaults, total counts, or whether results are paged by the Teamleader API — meaningful gaps for a 10-param list tool with no output schema.

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 sentences plus a short API reference; the resource is front-loaded, the returned fields precede the filter list. No filler or redundancy.

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?

Ten optional params and no output schema, but the description compensates by naming the fields returned, which is the most important missing piece. What remains unaddressed is pagination behavior and sort semantics, minor gaps that annotations and the schema largely fill in.

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 80%, so the schema already documents page, page_size, customer_type and most filter params. The description restates the filter dimensions (customer, deal, department, status, invoice) without adding format, combinability, or array/single-value semantics beyond what the schema provides, so baseline 3 fits.

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 ('List') and resource ('subscriptions (recurring invoices)'), and enumerates the key fields returned (title, status, customer, billing cycle, next invoice date). The plural/list framing plus explicit filters clearly separates it from the sibling teamleader_get_subscription and from teamleader_list_invoices.

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?

Names the filter dimensions (customer, deal, department, status, invoice), which implies when to reach for this tool, but gives no explicit when-not conditions or pointers to alternatives such as teamleader_get_subscription for a single record. Usage is inferable rather than stated.

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