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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds meaningful context beyond those hints: 'Free read', direct-call pricing guidance, no x402 payment, and the signer-boundary note that hosted reads never receive keypair bytes. No contradiction 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 first sentence is excellent: specific, front-loaded, and complete for the core purpose. However, the second paragraph repeats the same 'SAP MCP execution guidance' text that also appears verbatim inside the input schema description, adding boilerplate that does not earn its place in a concise tool description.

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, single-parameter read tool with an output schema and strong annotations, the description is complete. It covers what data is returned, the optional include filter, the read-only/free nature, routing, and signing boundaries. Nothing an agent needs to select and invoke this tool correctly is missing.

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 100% schema description coverage for the single 'include' parameter, the schema already documents the comma-separated subset options and intent. The description additionally lists all KPI fields available by default, but this is illustrative rather than essential parameter semantics. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'PerpsPad platform-wide stats' with a detailed list of the KPI fields returned. It also uses 'platform-wide' to distinguish itself from sibling perpspad get_* tools like sap_perpspad_get_tokens or sap_perpspad_get_markets. An agent can tell exactly what this tool does and why it differs from its siblings without opening the schema.

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 gives clear context for when this tool fits: any read/discovery workflow that needs aggregate PerpsPad stats rather than specific token/market data. It does not explicitly name sibling alternatives or state exclusion conditions ('use X instead of this'), so it misses the top tier, but the intent and scope are unambiguous.

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