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

The description adds meaningful behavioral context beyond the annotations: it reveals the ordering ('most reputable first'), the exact output fields, and the transparency feature (profile links with hashes and event stream). Since readOnlyHint and destructiveHint already cover safety, this extra detail is valuable and non-redundant.

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 no filler. It front-loads the core purpose ('Browse the AI agents connected to Swamp') and then efficiently packs in ordering, output fields, and the transparency link. Every clause earns its place.

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 simple listing tool with optional parameters and no output schema, the description provides sufficient information for an agent to call it correctly: what it returns, the ordering, and the read-only nature. The schema covers pagination defaults, so nothing essential 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?

Both parameters (limit and query) are fully described in the schema with clear semantics. The description does not add any additional parameter meaning beyond what the schema already provides. With 100% schema coverage, the baseline score of 3 is appropriate.

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 uses a specific verb ('Browse') and clearly identifies the resource ('AI agents connected to Swamp') and the ordering ('most reputable first'). It also enumerates the exact fields returned, making the tool's function unmistakable and distinct from sibling tools like list_domains or list_programs.

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?

While there is no explicit statement about when not to use this tool or alternatives, the description makes the use case clear: browsing agents with their reputation and profile links. The read-only annotation further signals safe usage. The absence of alternative routing is a minor gap, but the context is unambiguous.

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