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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the endpoint (GET /invoices) but says nothing about pagination behavior, result caps (limit max 100) or whether filters combine as AND — modest added value beyond annotations.

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 terse fragments, front-loaded with the resource and its returned fields, then filters, then endpoint. Nothing is wasted, though the telegraphic style borders on under-specification rather than genuine economy.

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?

With seven optional parameters, no output schema, and full schema coverage, the description supplies the one thing the schema cannot — the shape of returned records (id, number, date). Pagination is handled in the schema via next_offset, so the remaining gap is minor.

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 seven parameters are already documented with defaults and ranges; baseline is 3. The description echoes the filter groups (order, series, issue date) which helps orientation but adds no syntax, format, or date-string details 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?

Names the resource (invoices) and enumerates returned fields (id, number, date), plus the filter dimensions, so it is distinguishable from the singular sellasist_get_invoice sibling. The verb is only implied by the tool name rather than stated in the description, keeping it just short of a 5.

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 phrase 'Filter by order, document series or issue date' implies a collection-retrieval use case, but there is no explicit when-to-use guidance or named alternative (e.g., use sellasist_get_invoice when you already have an id). 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.