list_next_reference_numbers

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. However, the description adds no additional behavioral context, such as whether the number is consumed, what 'next' means, or the return format. It provides no value beyond the 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?

The description is a single sentence, which is extremely brief, but this is under-specification rather than effective conciseness. It omits critical details and is misleadingly vague, so brevity hurts rather than helps.

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?

The tool has no output schema, so the description must explain what the return value is. It fails to define 'next reference number', and the singular/plural mismatch between the name ('list_next_reference_numbers') and description ('Get next reference number') adds confusion. Overall, the information is insufficient for correct invocation.

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?

There are zero parameters, so the input schema fully covers the parameter set (100% coverage). The description does not need to explain any parameters; baseline 4 is appropriate.

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 'Get next reference number' is a near-tautology of the tool name 'list_next_reference_numbers' and does not clarify what type of reference numbers are involved or whether it returns a single number or a list. It also fails to distinguish the tool from siblings like list_purchase_document_numbers or list_expense_document_numbers.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of specific scenarios, prerequisites, or exclusions, leaving the agent without context to select it appropriately among many similar list tools.

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