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

Goes well beyond the readOnly/idempotent annotations: it discloses the paywall (0.01 USDC per get on eip155:8453), that a missing id still costs the stated amount, that an unsigned call returns a free payment quote rather than content, and that returned content is untrusted data, not instructions. This is exactly the payment/auth/injection context an agent needs.

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?

Front-loads the core action and return shape in the first sentence, then layers payment and untrusted-content detail. It is dense and packed but nearly every clause carries operational weight; the only mild bloat is the embedded product/pricing specifics, which are nonetheless actionable.

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 0% parameter coverage, the description supplies the missing information: return values (entry or null, untrusted_content, request_hash), the alternate quote response for unsigned calls, and the cost model. Nothing essential for correct invocation is missing.

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?

Schema description coverage is 0%, so the description must carry the load, and it does: id is explained as a publish_information entry_id or search_information entry id, and request_id as a UUID for a new operation (idempotency-style). It adds real meaning, though it does not clarify request_id reuse semantics explicitly.

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?

States a specific verb and resource ('retrieve one record using id') and explicitly ties the id source to sibling outputs ('from publish_information entry_id or a search_information entry id'), which distinguishes it from search_information and list_products. An agent can tell exactly what this returns without opening the schema.

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?

Gives clear usage context: this is the single-record fetch keyed off ids produced by publish_information or search_information, and it is the paid read path. It does not state explicit exclusions (e.g., 'do not use for listing/searching'), so it stops short of the 5-tier routing guidance.

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