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

With no annotations present, the description carries the full burden and does add real context: it is free, needs no authentication, and is a single-call consolidated read. It discloses the scope of what comes back (chain list, fees, tool counts, protocol list) rather than just saying "get info," though it does not state the response format.

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?

Three short sentences, front-loaded with the core verb and payload contents before the usage nudge. The dense enumeration of chains, tool counts, and protocols is information an agent needs, so it earns its space rather than padding.

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?

No output schema exists, so the description must convey what returns — it does so at a summary level (chains, fees, tool counts, protocol names). An agent knows enough to call it and roughly what to expect, though the exact response shape remains unspecified.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies a no-argument call by describing a single consolidated fetch.

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?

States a specific verb and resource — retrieve the full Synmerco platform surface — and enumerates exactly what that surface comprises (4 chains, fees, 52 MCP tools, 6 protocols). No sibling tool does capability discovery, so it is unambiguously distinguishable from the escrow, wallet, and search siblings.

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?

"Use this to teach your agent what Synmerco can do" gives a clear trigger for calling it, and "Free, no auth required" removes any prerequisite barrier. It stops short of naming an explicit alternative or when-not-to-call condition, which keeps it out of 5 territory.

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