create_mcf_order

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

With no annotations, description carries full burden. Only labels as 'guarded write' and notes it's a stub locally, but lacks details on success/error behavior, required permissions, rate limits, or side effects beyond writing.

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?

Two concise sentences that front-load the key action and important caveat about the local server being a stub. No unnecessary words, every sentence adds value.

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?

Missing critical context: no output schema, no explanation of return values, no required fields despite schema having no required parameters. The 'guarded write' concept is mentioned but not explained, and the stub aspect is noted but doesn't inform actual behavior.

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% with generic descriptions, but the tool description itself adds no information about parameters. Does not explain how parameters like 'preview', 'dry_run', or 'changes' map to the MCF order creation process.

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?

Clearly states the tool submits an MCF order request from FBA inventory, using specific verb 'Submit' and resource 'MCF order request'. Differentiates from sibling 'get_mcf_orders' and other create tools by noting 'guarded write' and 'hosted endpoint only'.

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?

No explicit guidance on when to use this tool over alternatives. Mentions it's a 'guarded write' but doesn't elaborate on prerequisites, when not to use, or how it differs from other create tools like 'create_listing' or 'create_keywords'.

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