transcribe_upload_append

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

The description lacks behavioral details beyond the basic action. It does not disclose error handling (e.g., consequences of duplicate chunk_index), idempotency, size limits, or the need for sequential chunk indices. No annotations are present to compensate.

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 (one sentence), which ensures clarity but at the cost of omitting crucial details needed for correct usage. A single sentence is acceptable only if the tool is self-explanatory, which it is not.

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 absence of annotations, output schema, and parameter descriptions, the tool description is severely incomplete. It fails to explain the upload session lifecycle, how this append step fits, or the expected behavior for errors.

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?

The input schema has 0% description coverage, and the tool description adds no meaning to the parameters. The agent cannot infer what 'upload_id' represents, the role of 'chunk_index', or the expected format of 'audio_base64' beyond base64 encoding.

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 action ('Append') and the resource ('one base64 chunk to an upload session'). It distinguishes from sibling tools like 'transcribe_upload_start' and 'transcribe_upload_finalize' by specifying the chunk appending operation.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., that an upload must be started first) or that finalization is required after all chunks are appended. The agent is left to infer the workflow.

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