tosea_export_presentation

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

No annotations are provided, so the description must carry the burden. It states it queues a job (implying asynchronous behavior), but does not mention that the presentation must be in a 'completed' state, permission requirements, or what happens on failure. Minimal behavioral context for a mutation tool.

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 two sentences, front-loaded with purpose, followed by focused usage guidance. No extraneous information, 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?

The description covers the main action and required parameters partially, but omits details on optional parameters and the asynchronous nature (e.g., returning a job ID for use with tosea_wait_for_job). Given the complexity of 4 parameters and no output schema, more completeness is needed.

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%, so the description should compensate. It adds meaning to 'output_format' by explaining when to use specific enum values, and implicitly covers 'presentation_id'. However, it does not explain 'export_filename' or 'idempotency_key', leaving two parameters undocumented.

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 'Queue an export job for a completed presentation', specifying the action (queue export) and resource (completed presentation). It distinguishes from sibling tools like tosea_list_exports and tosea_redownload_export, which deal with listing or re-downloading exports.

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?

The description gives explicit guidance on when to use specific output formats ('Use output_format='pptx_image' when...', 'Use html_zip only for...'). However, it does not explicitly contrast with alternative tools (e.g., use tosea_list_exports to check status), leaving some ambiguity.

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