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

With no annotations, the description carries the full burden, and it does disclose the network-wide scope, the record shape, and that the call is free (no cost/credit consumption). It does not state that this is a read-only, non-mutating call, nor describe ordering, pagination beyond the limit, or any rate limits — real gaps 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?

One sentence, front-loaded with what the tool returns, zero preamble. The long field enumeration partially duplicates the output schema, but it is compact and readable enough that it does not waste much space.

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?

An output schema exists, so return values need not be re-explained, and the description covers scope and cost. However, with no annotations the description should say this is a safe read and how results are ordered/paginated; those omissions leave it only minimally viable for a feed tool.

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 coverage is 100% for the single limit parameter (range 1-200, default 50), so the schema already does the work and the description adds nothing about it. Baseline 3 applies when structured data carries parameter meaning.

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 resource and scope: the newest attestations across the whole MINT network, which implicitly distinguishes it from per-agent tools like mint_trust_history. The parenthetical enumerates exactly what each record carries (agent, summary, trust score, confidence, anchor status, merkle root/Solscan). It stops short of naming a sibling it is not, so it lands at 4 rather than 5.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternative is named (e.g. mint_trust_history for a single agent, mint_verify for a specific attestation). The only selection signal is the trailing 'FREE', which hints at cost but does not tell the agent when this feed is the right call versus the other 15 mint_* tools.

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