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

The description adds significant context beyond the annotations: it requires an Authorization header, explicitly lists what the read does NOT return, and clarifies that only verified webhook fulfillment credits a quote. This gives the agent a clear picture of the tool's behavior and limitations.

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 concise yet informative: three sentences, each adding value. It front-loads the core purpose, then covers authentication and response limitations without unnecessary fluff.

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?

Given that an output schema exists, the description need not explain return structure. However, it compensates by clarifying important behavioral nuances (auth requirement, excluded fields, credit condition), making the tool's usage safe and unambiguous.

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 fully documents the sole parameter (quote_id) with a clear description and reference to create_funding_checkout. The tool description does not add additional semantic value for the parameter beyond what the schema already provides, so a baseline score 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 clearly states the tool's function: reading the lifecycle status of an MCP funding quote. It specifies the resource (funding quote) and the operation (read), and distinguishes it from siblings like get_balance and get_status by focusing on quote status.

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 the primary use case (checking funding quote lifecycle status) and states a prerequisite (Authorization header). It does not explicitly mention alternatives or when not to use, but the context is clear enough to infer proper usage.

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