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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description redundantly confirms "Read only." The genuine added value is the caveat that being listed confers no trust score or proof-of-outcome record, which prevents a false inference an agent could otherwise make from the listing. It does not mention pagination or result-size behavior.

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?

Three short sentences, front-loaded with the core action and the returned fields before the trust caveat. The closing "Read only" duplicates the readOnlyHint annotation and could be dropped without loss.

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?

With no output schema and no parameters, the description carries the return-value burden and does so by naming each field, including the sellerAgentId. The one missing piece is whether the listing is complete or paginated and roughly how large it is.

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 takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description instead spends its words on the shape of the response, which is the more useful information here.

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 opens with a specific verb and resource ("Lists the live data offerings on Paylyte") and enumerates the returned fields, so an agent knows exactly what it gets back. It does not explicitly name the siblings buy_live_offering or get_track_record, but "lists" is plainly distinct from a purchase action.

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 explicit when-to-use or when-not statement. The caveat that a listed seller has no Agent Trust Score or Proof of Outcome record from listing alone implicitly routes the agent to get_track_record for trust checks, but the connection is left for the agent to infer rather than stated.

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