akai_media_prep

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It says nothing about idempotency, destructiveness, authentication, rate limits, side effects, or output format. This is a critical gap for a media operation 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 extremely short (one sentence) but lacks essential information. This is under-specification, not conciseness. It fails to earn its place by omitting necessary details.

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 tool's likely complexity (media preparation), the absence of behavioral info, output schema, and clear purpose makes the description severely incomplete. It does not equip an agent to invoke the tool correctly.

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?

Input schema has 100% description coverage: 'args' and 'stdin' are explained. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate. No additional value provided.

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?

Description 'AkaiMediaPrep operator. (category: media)' is a tautology that merely restates the tool name and adds a generic category. It does not specify what action the tool performs or what resource it operates on, providing no useful purpose clarity.

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?

There is no guidance on when or how to use this tool compared to its many siblings (e.g., akai_render, akai_transcribe). The description offers no context for appropriate usage scenarios or alternatives.

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