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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context beyond this: it identifies the data source (Adrena Data API) and the SAP MCP guidance about pricing and signer boundaries for value-moving results. No contradiction with annotations exists.

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 opens with a clear, front-loaded sentence that captures the core purpose. The subsequent SAP MCP guidance block is somewhat verbose and repeated verbatim in the input schema, but it is structured and relevant to invocation. Overall, it is appropriately concise for the tool's simplicity.

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 single-parameter read tool with an output schema, the description covers the key data returned and provides routing/pricing guidance. However, given the large set of sibling Adrena tools, it lacks explicit disambiguation (e.g., when to use this vs. sap_adrena_get_trader_leaderboard). The output schema would clarify return shape, but the description alone leaves some contextual 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?

The input schema has 100% description coverage for the single 'wallet' parameter ('Trader wallet public key (base58)'), which is already clear. The tool description adds no additional parameter-specific meaning beyond what is in the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the tool fetches trader performance metrics for a specific wallet from the Adrena Data API, and enumerates the returned fields (total volume, P&L, fees, win rate, rank). This gives a specific verb+resource+scope and distinguishes it from sibling tools like sap_adrena_get_positions or sap_adrena_get_trader_leaderboard by focusing on individual performance metrics.

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 clearly implies when to use the tool: when a trader's performance metrics are needed for a given wallet. It does not explicitly name alternatives or exclusions, but the context is clear and the SAP MCP execution guidance provides routing and pricing context for invocation. Compared to siblings, no explicit 'vs.' guidance is given, so this is a 4 rather than a 5.

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