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

No annotations are provided, so the description carries the full burden of behavioral disclosure — and it discloses nothing. It does not state whether this is a safe read-only query, what network assumptions exist, whether parameters are required in practice, or what the response contains. With no output schema either, the agent has zero behavioral context.

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 text is only six words long but that is under-specification, not conciseness. Every word is redundant with the tool name itself, so no information is actually packed in. There is nothing front-loaded because there is nothing substantive to front-load.

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?

With no annotations, no output schema, three optional-looking parameters, and a sibling set of roughly 2,000 tools including direct analogues, this definition is far below minimum viability. An agent cannot construct a correct call with confidence — it only has the 'info' suffix and generic schema labels to go on.

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?

Schema description coverage is 100%, so the baseline of 3 applies even though the description mentions no parameters directly. However, the schema labels ('Chain to process', 'Token to process', 'Address to process') are semantically weak — 'Token to process' could mean a contract address or a token ID — and the description does nothing to clarify formats, valid values, or which of the three optional parameters are actually required.

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 'Ercc1155 Info: Erc1155 Info' is a pure tautology — it restates the tool name and nothing else. There is no verb, no resource scope, and no indication whether it returns balance, metadata, total supply, or ownership. Amid siblings like erc20-info, erc721-info, and nft-metadata, an agent cannot tell what this tool actually does.

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 offers zero guidance on when to call this tool or which alternatives apply. The sibling list contains closely related tools (erc20-info, erc721-info, nft-metadata, token-intel), but nothing here helps the agent choose between them. No exclusions, no conditions, no prerequisites — the agent is left guessing.

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