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

With no annotations, the description is the sole source of behavioral disclosure. It hints at a read-only 'line-up' and 'played back as notes,' but never explicitly states that the tool is read-only, whether it returns data, or what side effects it might have. This is insufficient for a tool with zero annotation coverage.

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 just two sentences with no fluff, and the core subject appears first. The metaphorical phrasing is slightly less efficient than a direct statement, but it still fits within a compact scope.

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 zero-parameter, no-output-schema tool, the description covers the main content ('which agents have a song, and their wallets' and 'on-chain history played back as notes') but does not provide a concrete return format or example. It is acceptable but has clear gaps.

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 tool has zero parameters and an empty input schema, so there is nothing the description needs to add about parameters. Per the baseline rule for 0-parameter tools, this gets full credit.

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 names a resource ('the city radio line-up') and indicates it shows which agents have a song and their wallets, but it never uses a clear verb such as 'get' or 'list'. It is vague about whether this returns a directory, plays content, or otherwise, and it does not distinguish itself from the sibling 'agent_tune'.

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?

There is no guidance on when to call this tool versus alternatives such as agent_tune or agent_vault_status. The description only describes the content, not the conditions that would make this the right choice.

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