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

With no annotations, the description carries the behavioral burden. It calls out 'FREE' (cost) and states 'where this data comes from' (provenance). It doesn't explicitly state there are no side effects, but for an informational tool the read-only nature is strongly implied.

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?

One dense sentence that leads with the most decision-relevant trait ('FREE') and packs the full scope into a compact list. No filler.

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 no-input informational tool, the description covers what the agent gets and the provenance of the data. It is slightly incomplete in not clarifying how this relates to how_to_pay or what output shape to expect, but the lack of parameters keeps the requirements low.

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 schema coverage is 100%, so the description has no parameter burden. Baseline 4 applies because there is nothing to document.

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 states the tool's subject area precisely: it covers AIS's product catalog, x402 purchasing, and data provenance. It lacks a direct action verb like 'returns' or 'provides,' but the content enumeration makes the purpose unmistakable and distinguishes it from siblings like how_to_pay and list_buildings.

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 makes the intended use context clear: an agent wanting an overview of AIS offerings and buying options. However, it never explicitly says when to prefer this tool over how_to_pay, and the included 'how agents can buy over x402' clause overlaps with that sibling.

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