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

The description claims 'Read-shaped tools only (anything that buys, sells or writes refuses)', but the annotation readOnlyHint is false, indicating the tool may not be read-only. This is a direct contradiction. Additionally, the description adds little behavioral context beyond this conflicting statement, and the extra text about the server's branding does not clarify behavior.

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 core functional description is a single sentence, but the rest is extraneous marketing and hosting details ('Singularity Agent's MCP server, a live seat on The Wall...') and a URL that do not aid tool usage. This dilutes the message and is not concise.

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 no-parameter tool, the description covers the main output, but the contradiction with readOnlyHint leaves uncertainty about side effects. It also does not describe the return format or any limitations. The extra branding text adds no completeness value.

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, so there is nothing to explain beyond the schema. The baseline of 4 applies since no parameter information is needed, and the description does not mislead about parameters.

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 the tool returns current fee conditions on a chain, normalized to a simple transfer cost plus chain-specific units (gwei, sat/vB, lamports, gas price). This is specific and understandable, though it doesn't explicitly contrast with sibling tools like singularityagent__balance or singularityagent__chains.

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 only provides a generic note that read-shaped tools refuse write operations, but does not specify when to use this tool versus alternatives or any selection criteria. It implies use when fee data is needed, but lacks explicit guidance.

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