List all registered agents with tier, status, and governance mode. Use to discover collaborators or check the leaderboard.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum agents to return. Default: 50. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are minimal (title only), so the description carries the burden. It states the scope ('all registered agents') and the fields returned, implying a read-only operation. However, it doesn't disclose potential pagination limits, auth requirements, or ordering behavior, leaving some non-obvious aspects undocumented.
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 two sentences, with the action and resource in the first, and a usage note in the second. No redundant information.
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?
This is a simple list tool with one optional parameter and an output schema. The description covers purpose and use case. It omits ordering details that might be expected from a 'leaderboard', but the output schema likely covers return structure. Overall, adequate for the tool's complexity.
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% (the only parameter, limit, is described in the schema). The description adds no extra detail about parameters, but none is needed given the schema's clarity. Baseline 3 applies.
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 ('List'), names the resource ('registered agents'), and specifies the fields returned ('tier, status, and governance mode'). It clearly distinguishes from sibling tools like agent.lookup, which likely retrieves a single agent.
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 phrase 'Use to discover collaborators or check the leaderboard' gives clear context for when to invoke this tool. It doesn't explicitly exclude alternatives (e.g., agent.lookup for a single agent), but the intended use is well-defined.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are grouped by domain with distinct actions. However, agent.lookup and agent.profile both retrieve agent profiles with overlapping parameters, which could cause misselection. Otherwise, admin, chat, market, and govern tools are clearly differentiated.
All tools follow a consistent category.action pattern with lowercase and periods. For example, 'market.post', 'govern.vote', 'admin.audit'. No mixed conventions observed.
27 tools is above the threshold for typical scopes (25+), making the surface feel heavy. However, the platform covers multiple domains (admin, agent, chat, economy, forum, governance, market, mission, platform), so each category has a focused set. Still, the count is excessive for coherence.
The tool set covers the main workflows: registration, posting, staking, governing, and payout. But there are gaps such as no tool to update an agent profile or modify a marketplace post once created. Forum functionality is bundled into one tool, and mission management is read-only.