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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful return-content context, including paused-reason visibility and the word 'Free', but it does not disclose pagination, ordering, permissions, or filtering behavior.

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 definition is a single compact sentence that front-loads the resource and then lists the exposed fields. The trailing 'Free.' is a fragment that may be useful but is structurally abrupt.

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?

Because there is no output schema, the description should carry the return-value burden, and it does list many returned fields. However, it omits the status filter's meaning and does not explain ordering, pagination, or result limits, leaving gaps for an agent deciding how to call it.

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 has one optional status parameter with enum values, but the description never mentions status filtering at all. With schema description coverage at 0%, the description should compensate by explaining what the status filter does; it does not.

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 names the specific resource, repeating invoices, and enumerates the details it exposes: recipient, lines, frequency, next dates, draft/sent state, generated count, last invoice, and pause reason. It is clear what the tool returns, though the verb is implied through the title rather than stated in the description itself and no sibling is explicitly contrasted.

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 invoices_list or invoices_get, nor any mention of prerequisites or exclusions. The only contextual cue is the implicit scope of listing repeating invoices.

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