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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds 'operation class read' and 'read/discovery workflow', which are consistent but do not substantially expand beyond annotations. No contradictions. No details on rate limits, data freshness, or the exact meaning of 'top gainers/losers' (e.g., percentage change calculation).

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 suffers from excessive SAP MCP boilerplate that is repeated in multiple places, including the input schema. The first sentence is concise, but the rest is long and cluttered with operational details (pricing, routing, signer boundary) that are better suited for documentation or system-level configuration. Every sentence does not earn 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?

The tool is simple with 2 params and an output schema exists, but the description lacks critical details: what the output contains (e.g., list of tokens with price change), sorting order, count of items, and whether vsCurrency is required. Without these, an agent may not understand the tool's full behavior. The SAP context is irrelevant to the functional completeness.

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%, but the descriptions are tautological (e.g., 'Duration parameter for Coingecko Get Top Gainers Losers'). The main description does not explain the parameters further. It does not clarify that vsCurrency is a base currency like 'usd' or what the duration values represent. The param semantics are not improved by the description.

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 'Get top gainers and losers from CoinGecko' which identifies the specific resource and action. The title and first sentence are unambiguous. However, the following SAP MCP text dilutes the clarity by mixing operational details with the core purpose. Sibling tools include other coingecko_* functions, so the tool is distinguishable as focused on gainers/losers.

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 vague advisory like 'Use for off-chain market data' without specifying when to prefer this tool over alternatives like coingecko_getTrending or coingecko_getTokenPrice. It does not mention exclusion criteria or alternative tools. The SAP routing info is not about usage context but about payment/execution mechanics.

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