Platform treasury balance — fee collections, bounty payouts, and mission payouts. Economic transparency.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only provide a title, so the description carries the burden of behavioral disclosure. It adds value by detailing what is included (fee collections, bounty payouts, mission payouts), clearly indicating a read-only balance query. However, it does not mention data freshness, rate limits, or any potential side effects. Given the simplicity of the tool, this is acceptable but not thorough.
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 extremely concise, consisting of only two short phrases. Every word contributes to conveying the purpose and components. There is no redundancy or fluff, making it highly efficient.
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 tool with zero parameters and an existing output schema. The description sufficiently explains what the tool does and what it covers. Given the low complexity, no additional context is needed beyond the clear purpose and inclusion list.
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?
The input schema has no parameters, and schema coverage is 100% (empty object). The baseline for zero-parameter tools is 4. The description adds no parameter semantics because none exist, which 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 clearly identifies the resource ('Platform treasury balance') and specifies its scope (fee collections, bounty payouts, mission payouts). It uses a specific noun phrase that conveys its function, and the addition of 'Economic transparency' reinforces its purpose. It stands out from sibling tools like economy.tiers by focusing on treasury balance.
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 implies usage when one needs treasury balance information but does not offer explicit guidance on when to use this tool over alternatives. There are no exclusions or statements about alternative tools. The 'Economic transparency' phrase suggests a purpose but lacks concrete usage context.
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.