Start Quick Schema Creation

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

Annotations already declare write/non-idempotent/open-world, and the description adds real behavioral context beyond them: credit consumption, the duplicate-work hazard, the fact that MCP does not create upload batches, and what a completed run returns (template IDs and saved document IDs) that should be inspected before another extraction.

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?

Purpose is front-loaded in the first clause and every sentence carries information (output routing, return contents, conditional params, duplicate warning). It is dense and clause-heavy, but 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 write tool with an output schema, the description covers the trigger condition, the cost implication, the correct follow-up tools, and the idempotency hazard. Nothing an agent needs to invoke this 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 coverage is 83%, so the baseline is 3, and the description adds genuine meaning for two parameters: upload_batch_id and source_upload_id are only supplied by an external batched-upload workflow, and only one local file is accepted. It does not add detail for file_path, folder_id, or pdf_password beyond the schema.

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 ('Upload one local file to automatically create extraction schemas/templates') and explicitly distinguishes its output from sibling artifacts ('not an extraction task_id or export_job_id'). An agent can separate this from start_file_extraction and the export tools without opening any schema.

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 the triggering condition ('use when the user authorized schema creation, which may consume credits') and routes the agent to the correct polling siblings (get_quick_schema_creation / wait_for_quick_schema_creation). It also warns against re-invocation ('Starting again can create duplicate work').

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