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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds one useful trait—'Browser-based tool'—which explains the lack of parameters, but it does not disclose what happens after generation (e.g., download, preview), whether login is required, or any side effects.

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 with a parenthetical note, containing no fluff or redundancy. Every word earns its place, and the key information (purpose and browser-based nature) is front-loaded.

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 zero-parameter browser-based tool, the description is minimally sufficient, but there is no output schema or explanation of what 'delivery notes with receipt confirmation field' means in practice (e.g., file format, preview vs. download). The description leaves some ambiguity about the tool's workflow.

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 tool has zero parameters, and the description's mention of 'Browser-based tool' clarifies that no inputs are needed. Since the schema is empty, there is no parameter documentation burden, and the description adds the key context of how the tool is invoked.

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 clearly states the tool's function: 'Generate delivery notes with receipt confirmation field.' It uses a specific verb and resource, and the term 'delivery note' distinguishes it from sibling tools like invoice-generator and receipt-generator, though it does not explicitly name them.

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 such as invoice-generator or receipt-generator. The description does not mention typical use cases, prerequisites, or exclusions, leaving the agent to infer when it is appropriate.

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