voicestudio_upload_base64

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

Annotations already declare the safety profile (readOnly=false, destructive=true, openWorld=true, non-idempotent), so the bar is lower. The description adds useful behavioral context beyond them: an 8 MiB default size limit, the staging nature of the operation, and a workflow anti-pattern to avoid. It does not explain what the destructiveHint implies (e.g. overwriting an existing staged file), leaving one gap.

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 tightly written sentences with no filler. The primary action and size cap are front-loaded, followed by the alternative and the anti-pattern guidance, in decreasing order of importance.

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 3-parameter mutation tool with no output schema, the description covers the workflow and the size constraint, and annotations cover safety. It stops short of the parameter-level detail (filename/mime_type behavior, overwrite semantics) and does not indicate what a successful stage returns (a handle or ID) that a caller probably needs to proceed.

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% and none of the three parameters have schema descriptions, so the description must carry the full load. It only clarifies content_base64 (base64 source, size capped) and leaves filename (does it overwrite an existing entry? is the extension meaningful?) and mime_type entirely 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 gives a specific verb ("Stage") and resource ("a small file ... from base64"), so an agent immediately knows what operation this performs. It also carves out the large-file case against the signed-PUT path, though it does not name the sibling tool (e.g. voicestudio_create_upload) explicitly. Clear purpose with slightly implicit sibling differentiation.

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?

It states the condition for use (small files, default 8 MiB cap), the alternative for large files (direct signed PUT upload), and a hard behavioral rule (never ask the user to paste base64 into chat). The when/when-not/alternative triad is all present.

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