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

The description offers a meaningful behavioral hint by noting the tool is 'Browser-based', indicating it likely operates via a UI rather than returning raw data. However, without annotations, it lacks details on what the agent should expect (e.g., output format, workflow). It adds some value beyond the name but is not thorough.

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 extremely concise, consisting of a single sentence plus a parenthetical. It front-loads the key purpose ('Invoice-compliant receipts with auto tax calculation') and adds a useful behavioral note. Every word earns its place with no redundancy.

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?

Given the simplicity of a zero-parameter, browser-based generator, the description provides sufficient context: it states what the tool produces, a key feature (auto tax calculation), and its browser-based nature. While it could detail the output format, the combination of these elements makes it reasonably complete for the tool's trivial complexity.

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, so the schema is trivially complete. The description adds no parameter information, but the baseline for 0 params is 4, and there is nothing missing since no inputs are required. The description effectively clarifies the tool's function without needing parameter details.

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 identifies the tool's output as 'Invoice-compliant receipts' with 'auto tax calculation', which distinguishes it from sibling tools like 'invoice-generator' and other document generators. Though it lacks an explicit verb, the tool's name and context imply generation, making the purpose unambiguous.

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 description provides no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions or when to choose a different generator, such as invoice-generator. The intended usage is only implied by the tool's name and description.

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