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

Beyond annotations (readOnly, idempotent, not destructive), the description adds 'Free read' and detailed SAP MCP execution guidance covering pricing, routing, and signer boundary (hosted reads never receive keypair bytes, value-moving results finalized locally). This provides actionable behavioral context not present in 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 opening two sentences are concise and informative. The SAP MCP execution guidance paragraph is generic boilerplate repeated across SAP tools, adding length but not tool-specific value. It's not overly verbose, and the critical info is front-loaded.

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 zero-parameter read tool with an output schema and comprehensive annotations, the description is complete. It provides usage context, pricing, routing, and security behavior. Nothing essential is missing for an agent to call it correctly.

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 tool has zero parameters, so there is nothing to document. Schema coverage is 100% (empty schema), and the description adds no parameter details because none exist. The baseline for zero-param tools is 4, but the description's clarity about the free-read nature effectively makes it perfect.

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?

States a specific verb and resource: 'List stock mints pairable for PerpsPad stock-paired launches', clearly distinguishing it from sibling tools like sap_perpspad_get_tokens or sap_perpspad_get_markets. The mention of 'stock-paired launches' and 'stock launch builder flow' pins down its exact role.

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?

Explicitly says 'Use with the stock launch builder flow', giving a clear context. It doesn't explicitly list alternatives or when not to use, but the context is enough to route an agent appropriately. The 'Free read' and routing guidance further clarify invocation expectations.

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