complete_media_replacement

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

No annotations provided, so description carries full burden. It only states completion action but does not disclose any behavioral traits like idempotency, failure states, or required authentication. Minimal transparency.

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?

Single sentence, no redundant words. However, it may be too brief for clarity; still efficient.

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?

Tool has 1 parameter, no annotations, and no parameter descriptions. The description does not explain the upload_id, output, or prerequisites. Incomplete for a mutation tool with no other context.

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 description coverage is 0%; the parameter 'upload_id' is not explained in the description. The description adds no meaning beyond the schema, failing to compensate for the gap.

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 tool completes a replacement after bytes are uploaded. It uses specific verb 'finish' and resource 'replacement', but does not distinguish from sibling 'complete_media_upload', which is similar.

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?

Implies usage after bytes have been PUT to a signed URL, providing a precondition. However, no explicit when-to-use or when-not-to-use guidance, nor alternatives like complete_media_upload.

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