tosea_create_document_parse

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

With no annotations, the description carries full burden. It reveals the output type (Markdown and image URLs) but omits behavioral details like whether files are kept, required permissions, rate limits, or side effects beyond creating a job.

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?

The description is extremely concise (15 words, one sentence), but this comes at the cost of missing essential details. It is front-loaded but under-informative for a tool with 12 parameters.

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?

Given the complexity (12 parameters, no output schema, no annotations), the description is severely lacking. It does not explain the job lifecycle, return values, or how to use parameters, making it nearly unusable for an agent.

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 0%, yet the description does not explain any of the 12 parameters. It merely mentions 'upload local source files' without describing required file_paths or optional parameters like instruction, render_provider, or template_name.

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 it uploads local source files and creates a parse-only document job returning Markdown and image URLs. The verb 'upload' and 'create' specify the action and resource. It distinguishes from other parse-related siblings like tosea_parse_pdf by emphasizing the parse-only job nature, but could be more explicit about differences.

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 guidance on when to use this tool vs alternatives such as tosea_parse_pdf or tosea_get_document_parse. No mention of prerequisites, context, or exclusions, leaving the AI to infer usage.

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