list_crypto_symbols

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

No annotations provided; description discloses return format and example but doesn't explicitly state it's read-only or safe. Adequate but not rich.

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?

Description includes docstring-style Returns and Example sections, which is slightly verbose. Could be more concise while retaining clarity.

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?

Fully describes return value (symbols, count, usage), provides example, and integrates with create_portfolio. Output schema exists to cover details.

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?

No parameters in schema; coverage is 100%. Description adds no param info, but baseline for zero-param tools is 4. No need for further explanation.

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?

Description clearly states the tool lists supported crypto symbols and CoinGecko IDs. It differentiates from siblings like search_crypto_coins and get_crypto_info.

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?

Description implies use for getting symbols to use with create_portfolio via the 'usage' field, but lacks explicit when-to-use or when-not-to-use compared to alternatives.

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