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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds 'operation class read' and 'paid read-premium' pricing, providing cost context beyond schema. No contradictions with annotations.

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 includes lengthy SAP MCP boilerplate that is duplicated in the input schema, making it verbose. The functional purpose is front-loaded, but the repetitive execution guidance detracts from conciseness.

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 has no parameters and an output schema exists, so output details are not required. The description includes integration guidance (e.g., estimating cost) but omits any detail about the return format or structure, leaving some gaps.

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?

With zero parameters, the schema fully describes the interface. The description adds no param info, which is acceptable as baseline is 4 for no-parameter tools.

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 trending tokens and NFTs on CoinGecko', identifying the specific resource and action. However, it does not explicitly distinguish from sibling tools like coingecko_getTokenPrice or coingecko_getTokenInfo, relying on the tool name for differentiation.

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 advises using it for off-chain market data as advisory context and notes that on-chain state is authoritative. It implies usage context but lacks explicit when-to-use or when-not-to-use comparisons with other tools.

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