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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the key safety-relevant behavior: discovery only, no order or payment. However, it does not mention any other behavioral traits such as authentication requirements, result size, or pagination, though the zero-parameter nature reduces the need for deeper disclosure.

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 two compact sentences with no redundant wording. The primary listing purpose is front-loaded, and the clarifying non-transactional statement is placed directly after it, earning its place by preventing misuse.

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 discovery tool with no output schema, the description provides enough context to understand what the tool returns conceptually (machine services and legal sellers) and what it does not do (create orders/payments). It could mention result format or availability constraints, but these are minor gaps given the tool's simplicity.

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 has zero parameters and 100% schema description coverage, so there is no parameter burden for the description to carry. Per the baseline for zero-parameter tools, a 4 is appropriate; no additional parameter documentation is needed.

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 uses a specific verb ('List') and a clear resource ('GovOmniAI machine services and legal sellers'), making the tool's purpose immediately obvious. It also explicitly contrasts with order/payment behavior, which helps distinguish it from the sibling transaction-related tools despite their opaque names.

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 phrase 'This is discovery only and does not create an order or payment' gives clear usage context and an explicit exclusion: it should not be used for transactional actions. It does not name alternative tools directly, but the behavioral boundary is strong enough to guide correct selection.

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