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

Annotations mark the tool as destructiveHint: true and idempotentHint: false, which are congruent—the description warns against blind retries causing duplicate swaps. It adds behavioral context beyond annotations by explaining the polling lifecycle and the need to check wallet activity first. The guidance on local finalization aligns with signer boundary rules, but doesn't detail all edge cases (e.g., gas fees), so not a 5.

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 front-loaded with the core action, first sentence stating the purpose. The polling instruction follows logically, then the error-avoidance tip, and finally the tier note. It's reasonably concise, but the embedded SAP MCP execution guidance is somewhat verbose and repeats schema-level information, which slightly detracts from focus.

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 is relatively complex (submission + polling), and the description explains the entire workflow: submit, poll, confirm, report txHash. It warns about duplicates and gives fallback actions. An output schema exists, but its content isn't shown; the description still covers the key return value (txHash). It could be slightly more explicit about error handling and providerRequestId usage, but is sufficient for an agent.

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%, and each parameter has a clear description. The tool description itself doesn't add much parameter-specific semantics beyond referencing that they come from the quote tool. It does mention signedTransaction is Base64 and beneficial for understanding, but this is already in schema. 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 states a clear verb ('Execute') and specific resource ('a signed Sunrise swap'), and explicitly references the companion tool sap_sunrise_get_quote that produces the input. It distinguishes itself from sibling tools like sap_sunrise_swap_intent by focusing on executing a signed transaction. The name is thus fully explained and differentiated.

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?

It gives concrete when-to-use guidance: use after obtaining a quote and user signature. It explains the polling procedure with exact statuses and how to avoid duplicate swaps on timeout. Also mentions routing to paid tool if needed, providing clear context for when to invoke this vs alternatives.

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