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

No annotations are provided, so the description carries the full burden. It mentions being 'Powered by the Fusebox SDK TradeModule' but does not disclose whether authentication is required, rate limits exist, or what side effects (none expected) occur. For a read-only tool, minimal transparency is provided.

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 two sentences with no filler. The first sentence defines the core function and qualifiers; the second provides source context. Every word earns 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?

Given no parameters and no output schema, the description is brief. It does not specify the output format (e.g., list of token addresses, symbols), pagination, or whether authentication is needed. For a simple list tool, it is minimally adequate but could provide more detail on the return structure.

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 and schema coverage is 100%, so baseline is 4. The description adds context by explaining that the returned catalogue includes tokens that are 'tradable, indexed, priced', which adds meaning beyond the empty schema.

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 'Returns the catalogue of ERC-20 tokens tracked by Fusebox (tradable, indexed, priced).' It specifies the verb (returns) and resource (catalogue of ERC-20 tokens), with qualifiers that distinguish it from sibling tools like 'fuse_get_token_price' or 'fuse_list_wallet_tokens'.

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 implies usage for obtaining a list of supported tokens but provides no explicit when-to-use guidance or alternatives. It does not differentiate from similar tools such as 'fuse_list_wallet_tokens' which lists user wallet tokens rather than the full catalogue.

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