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

Annotations already declare a non-read-only, open-world, non-idempotent, non-destructive call, so the bar is lower. The description still adds substantive behavior the annotations cannot convey: reply from hello@solidmade.co within one business day, one fixed price, nothing starts and nothing is charged until the user agrees.

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?

Three sentences, consequence-first ordering: what it does, the consent gate, then the outcome and no-charge guarantee. No sentence 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 five-parameter outbound request tool with no output schema, the description covers consent, response channel and timeline, and cost safety. It stops short of failure/retry behavior or what the agent should do with the incoming quote, but nothing essential to invoking it correctly is missing.

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 description coverage is 100%, so every parameter including the optional budget and service_id is already documented. The description adds no format, syntax, or validation detail beyond the schema, so the baseline 3 applies.

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 (sends) and resource (a job request to Solidmade on the user's behalf), and the title pins down the outcome as a fixed price. It is unmistakably distinct from the read-only siblings get_service and list_services.

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 an explicit precondition: 'Only call it after the user agrees to share their email and site link.' That is real gating guidance, though it never names the sibling workflow (browse with list_services first, reference service_id) that naturally precedes this call.

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