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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it's a 'Free read' and includes SAP MCP execution guidance about calling directly without x402 and signer boundary details, which are valuable context beyond annotations. It doesn't mention rate limits or specific response format, but the output schema covers that, and the safety profile is fully covered.

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 efficient and front-loaded: the core action ('Get one Backpack ticker snapshot... by symbol') appears first, followed by symbol format guidance, then the SAP MCP boilerplate. The SAP MCP guidance ('Call directly without x402', 'keep it small/exact') is duplicated in the input schema description, which is redundant, but the overall structure is tight and readable.

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?

For a simple one-parameter read tool, this is largely complete. The description covers symbol format, market types, examples, and pricing. The output schema (not shown but indicated) presumably details the returned fields, so that's covered. The only minor gap is explicit mention of what happens if the symbol is invalid or nonexistent, but for a straightforward read-only call this is acceptable.

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 coverage is 100% - only one parameter 'symbol' is documented in the schema. However, the description enriches it substantially with symbol format examples (SOL_USDC), market type distinctions (SPOT|PERP), and stock variants (MU.US_USDC, RFQ). This is crucial disambiguation that the schema alone doesn't provide. The description adds significant semantics beyond a bare symbol string.

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 ('Get'), a resource ('one Backpack ticker snapshot'), and lists the exact fields returned (lastPrice, bidPrice, askPrice, volume24h). It distinguishes itself from siblings like sap_backpack_get_tickers (plural) by emphasizing 'one' snapshot. The symbol example and market type enumeration (SPOT|PERP) clarify scope precisely.

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 explains the symbol format (SOL_USDC), market types (SPOT|PERP), and notes stock variants (MU.US_USDC, RFQ), providing clear context for when this tool is appropriate. It doesn't explicitly exclude alternatives like sap_backpack_get_markets or get_tickers, but the singular 'ticker' and field list imply this is for a single symbol snapshot. The 'Free read' note and SAP MCP guidance about calling directly are useful but are more related to pricing/routing than tool selection.

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