growwer_download_seller_order_draftDownload the current draft file for a seller's post order by providing its ID, so sellers can retrieve the exact draft they need to review or share.
Use this when the user, as a seller, needs the current draft file of a post order they sell: returns the file.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds only 'returns the file', without saying whether the result is a URL, binary payload, or where the draft comes from. Modest added value beyond structured fields.
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?
A single front-loaded sentence with no padding. Slightly awkward phrasing ('post order they sell') keeps it from being a clean 5, but nothing is wasted.
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 one-parameter, no-output-schema download tool the description covers the essentials of when and what. It omits the return shape (file vs link) and the precise meaning of 'id', which matter for correct invocation.
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?
There is one required parameter, 'id', with 0% schema description coverage. The description implies it is the id of the order being sold but never states that explicitly, nor whether it is an order id versus a draft id — the single most important ambiguity here goes unresolved.
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 and resource: it downloads/returns 'the current draft file of a post order they sell'. The seller qualifier distinguishes it from growwer_download_order_draft, but the phrase 'post order' is odd and the object of the download is only loosely named.
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?
'Use this when the user, as a seller, needs the current draft file' gives a use condition tied to the seller role. It does not name exclusions against closely related siblings such as growwer_download_order_draft or growwer_download_seller_order_briefing, leaving the agent to infer which download to pick.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.