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

With no annotations, the description carries the full burden of disclosing behavior. It mentions 'Browser-based tool' as a minor trait and lists features (delivery terms, tax calculation), but does not disclose side effects, permissions, data mutations, or output behavior. This is insufficient for an agent to anticipate the tool's 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 no filler words. Every phrase ('Purchase orders', 'delivery terms', 'tax calculation', 'Browser-based tool') conveys distinct information, and it is front-loaded with the core topic. This is appropriately concise with zero waste.

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 complete absence of annotations and output schema, the description must be the sole source of context. It fails to clarify the primary action or outcome of the tool (e.g., does it generate a document, calculate totals, or provide a form?), leaving the agent unable to confidently select this tool among many finance-related siblings.

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 input schema is empty with no parameters, so the baseline is 4. The description does not add any parameter details, but since there are none, it does not need to compensate. The description also does not introduce any ambiguity about parameters.

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 identifies the tool as relating to purchase orders, delivery terms, and tax calculation, but lacks an explicit verb indicating what the tool actually does (e.g., create, generate, manage). This makes the purpose somewhat vague and not clearly differentiated from sibling tools such as purchase-cost-manager or quote-generator.

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?

There is no guidance on when to use this tool compared to alternatives. No alternative tools are mentioned, no use cases are described, and no exclusions are provided. The only contextual hint is 'Browser-based tool,' which does not inform selection.

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