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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the write/external nature is known. The description still adds real value beyond them: Rich replies by email within one business day with a price and payment link, the person pays in a browser, and 'nothing is charged here' — setting latency and payment expectations. It does not describe failure modes (e.g. what happens if the email is invalid or the file link is unreachable).

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?

Front-loaded with the action and the consent constraint, then the required detail, then the file-optional branch — a sensible order. The final sentence is long and clause-heavy, and the quote/pay mechanics could be tightened, but nothing is filler.

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 10-parameter, 90%-covered, no-output-schema tool, the description covers intent, consent, required detail, file handling, and what the requester receives. The remaining gaps — the manual-quote requirement behind requested_material and the boundary against quote_custom_print — are mostly carried by the schema.

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 90%, so the baseline is 3, but the description adds meaning the schema lacks: the file is optional, accepted formats are STL, OBJ, 3MF or STEP, or Printables/Thingiverse/MakerWorld model links, and with no file the item is described with measurements and designed plus printed as a combined quote. That materially clarifies file_url and the no-file path.

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 concrete verb and resource ('Send a quote request to Rich at DrMaker3D') plus the target user ('a person who wants something 3D printed or designed'), so the action is unmistakable. It does not explicitly contrast itself with the sibling quote_custom_print (instant vs. hand quote), leaving that differentiation to be inferred from the file_key schema text.

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?

Gives clear preconditions ('only with the person's permission, and only with their own name and email') and tells the agent what to supply: description, size, material/color, quantity, deadline. It stops short of naming when to route to quote_custom_print or create_checkout instead, so routing to siblings is only implied.

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