export_create

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

Discloses that the tool is state-changing and may cost credits, which adds behavioral context beyond the schema. No annotations were provided, so the description carries the full burden; it does not contradict any annotations.

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 information. No unnecessary words, but could be slightly more structured (e.g., separate lines for requirements and effects).

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?

Incomplete for an 8-parameter tool with no output schema: missing parameter details, return value, error handling, and async behavior. Only addresses cost confirmation.

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?

With 0% schema description coverage, the description adds minimal meaning: only mentions confirm_cost requirement without explaining its role or other parameters like model, format, or imgsz.

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 verb 'Create' and resource 'model export job', and distinguishes from siblings like exports_list and export_status by indicating it's state-changing and may cost credits.

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?

Provides explicit requirement for confirm_cost=true, which is a clear usage guideline. However, it does not explicitly state when to use this tool versus alternatives like exports_list or export_status.

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