List the latest on-chain agent registrations

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the live source (three.ws /api/deployments feed), that it indexes external registrations, the newest-first ordering, and the fields returned in each entry. It adds meaningful behavioral detail without contradicting annotations.

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 three tigh t sentences: purpose and source, return fields, and optional parameter plus read-only note. It is front-loaded and every sentence contributes essential information with 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 read-only list tool with no output schema, the description covers the key completeness aspects: data source, sorting, per-entry fields, cross-chain option, and safety. Pagination is missing but cursor is documented in the schema, and the openWorldHint aligns with the live feed statement.

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 100%, so the baseline is 3. The description adds minor semantic value by explaining all_chains as 'same stream' and referencing limit/cursor context indirectly, but most parameter behavior is already fully documented in the schema.

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 states what the tool does: it lists the latest on-chain agent registrations in the Metaplex Agent Registry, newest first, from a specific live feed. It differentiates from sibling tools like get_onchain_agent by emphasizing the list/stream nature and the source, making its purpose unambiguous.

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 provides clear context for when to use the tool: to see the most recent agent registrations, with a note on including EVM registrations via all_chains. It implicitly contrasts with single-fetch tools and declares the operation read-only, but does not explicitly name alternatives or state when not to use it.

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