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

With no annotations, the description carries the full burden of behavioral disclosure. It does not explicitly state that the tool is read-only, nor does it mention data freshness, caching, or whether results are a summary or a detailed breakdown. The listed content categories are helpful, but the absence of explicit non-mutation guarantees and other behavioral context is a significant gap for an unannotated tool.

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 concise: two sentences, with the five content categories front-loaded and a clear use-case statement at the end. Every sentence earns its place, and there is no filler or 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?

For an empty-parameter tool with no output schema, the description covers the key content categories, which is essential. However, it does not specify how the return data is organized, whether it is a single aggregated view or separate sections, and it lacks guidance on choosing this over sibling list endpoints. The absence of behavioral notes further limits completeness.

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 baseline is 4. There are no parameter details for the description to explain, and the content list already tells agents what information they can expect.

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 as a 'comprehensive market overview' and enumerates concrete content areas: prices, availability, allowed durations, order constraints, and transaction types. It is specific about the resource and scope, though it does not explicitly distinguish itself from overlapping siblings like get_prices or get_available_resources, relying on the word 'comprehensive' to imply a superset view.

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 offers a general use case ('useful for agents to understand what they can purchase') but gives no guidance on when to prefer this tool over alternatives such as get_prices, get_available_resources, or get_orders. It does not state any exclusions or conditions, leaving tool selection to inference in a crowded sibling list.

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