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. The description adds the underlying endpoint (GET /invoices/number-sets) and the id-consuming relationship, but says nothing about result volume beyond the schema's paging params or ordering.

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 tight sentence: resource definition first, then the actionable instruction, then the endpoint. No filler and nothing important buried.

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 two-param, no-output-schema list tool this covers purpose, the shape of the results (number sets with ids), and how to use them downstream. Slightly short of complete because it doesn't hint at other fields returned or ordering, and doesn't contrast with invbg_get_next_invoice_number.

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 coverage is 100% and both parameters (page, per_page) are fully documented in the schema, including the next_page chaining hint. The description adds no input-parameter detail of its own; its extra meaning concerns the returned id, not the inputs. Baseline 3 applies.

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 the exact resource (the company's invoice number sets, glossed as separate numbering series), notes that ids are returned, and ties it to a consumer (invbg_create_invoice). The parenthetical definition alone distinguishes it from sibling list tools like invbg_list_invoice_types.

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?

Explicitly says to pass an id as number_set to invbg_create_invoice, which tells the agent the concrete situation this tool serves. It does not address the nearest alternative, invbg_get_next_invoice_number, so the when-not guidance is missing.

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