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

Annotations show readOnlyHint: false and idempotentHint: false, so the description does not contradict them. It adds useful context about the SAP MCP workflow, including pricing and signer boundaries, which is beyond annotations. However, it doesn't fully disclose all behavioral traits (e.g., the exact response format or side effects), but it's adequate.

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 moderately concise and front-loaded with the core function before the SAP-specific guidance. The SAP section is repetitive and could be trimmed, but it's not excessively verbose.

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 tool with an output schema and high parameter coverage, the description covers essential operational context: the purpose, parameter usage, and the paid-tool routing. It could mention return data details, but output schema covers that. Overall, it's sufficient for an agent to invoke 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?

Schema coverage is 100%, so parameters are well-documented. The description adds clarification that amounts are strings for precision and explains the difference between amount and amountRaw. This is valuable beyond the schema's own descriptions, though not exhaustive.

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's function: quoting an exact-in buy or sell on a specific Meteora DBC curve or its graduated DAMM v2 pool. It names the resource and the action, and it differentiates from siblings by mentioning the specific pool type, though it doesn't explicitly name sibling tools.

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 implies usage context (when you need a quote for a trade on Meteora) and provides guidance on the SAP MCP payment workflow, but it doesn't explicitly state when not to use this tool or mention alternatives. The payment routing instructions are clear but specific to the SAP environment.

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