getCryptocurrencyList

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety and world-scope profile is covered. The description adds scope ('all cryptocurrencies traded on exchanges worldwide') but says nothing about result size, pagination, or whether the response is a flat symbol list versus per-asset detail records — a real ambiguity given the phrase 'detailed information on each cryptocurrency'.

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 first sentence carries the useful content but is padded with 'FMP Cryptocurrencies Overview API'. The second sentence is pure marketing filler ('to inform your investment strategies') and adds no operational information an agent can act on.

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?

This is a simple zero-parameter list tool with annotations covering its safety profile, so not much is required. However, with no output schema, the description should have clarified what a returned record actually contains — 'detailed information' is too vague to set expectations about fields.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the schema fully covers the empty input object.

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 states a specific verb and resource: retrieving a list of all cryptocurrencies traded on exchanges worldwide. The resource name and scope distinguish it naturally from siblings like getCryptocurrencyQuote or getCryptocurrencyHistoricalLightChart, though it never explicitly contrasts itself with the adjacent listCommodities or getForexList.

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?

There is no when-to-use guidance and no mention of alternatives. The only usage framing is the generic 'to inform your investment strategies', which does not tell an agent when to pick this list endpoint over a quote or chart endpoint.

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