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

Annotations are minimal (readOnlyHint false, destructiveHint false), so the description should disclose behavioral traits like network calls, data freshness, or error handling. The description mentions 'data comes back as it is' and 'called through their seat' but provides vague meta-context rather than actionable behavior. It does not contradict annotations, but it falls short of carrying the burden for an open-schema tool.

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 bloated with promotional and server-level details: 'Singularity Agent's MCP server', 'a live seat on The Wall (hosted by them)', and a listing URL. The core purpose is front-loaded, but the extra paragraphs distract and reduce scannability. Every sentence does not earn 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 an open-schema tool with no output schema, the description should specify the expected input format (e.g., parameter name, how to pass the string) and the shape of the return value (e.g., a list of chains with confidence). The description only hints at 'resolves names to addr' and does not clarify output structure or pagination, leaving the agent to guess how to interpret results.

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 schema is open (additionalProperties true) with 0 formal parameters, so the description is the only source of parameter meaning. It explicitly states the tool takes 'an arbitrary string' and lists example types, giving the agent a clear semantic cue for the expected input. It could be more precise (e.g., naming the parameter), but it compensates well for the schema's lack of structure.

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 resolves an arbitrary string into a known type (address, transaction hash, ENS/SNS name, or block height) and identifies possible chains. This is a specific verb-resource pair that distinguishes it from generic search tools. However, it does not explicitly differentiate from other singularityagent__ tools like decode or transaction, so it's not a 5.

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 gives context about what the tool does and notes it is 'read-shaped' (no buying/selling/writing), which helps agents know when to use it for read-only resolution. But it does not explicitly state when NOT to use it or name alternative tools for similar purposes, leaving usage decisions partially inferred.

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