prepare_for_ai

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

With no annotations, the description carries the burden. It discloses that only paths are accepted (no inline base64) and mentions default behavior. However, it does not cover side effects (e.g., file deletion), permissions, or output format. The transparency is moderate.

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 with two sentences, each carrying essential information. It is front-loaded with 'One-shot AI prep' and efficiently covers key behavioral aspects.

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 3 parameters and no output schema, the description is insufficient. It does not explain return values, processing details, or prerequisites. The tool's behavior for job_id and non-default profiles is unclear. Completeness is low.

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%, but the description adds meaning: 'Paths only' for path, and 'default' for profile. It does not explain job_id or other enum values. The description partially compensates but is incomplete.

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's purpose: 'One-shot AI prep' for images and videos. It specifies actions (resize/compress for images, frame pack for videos) and distinguishes from sibling tools like image_compress and video_extract_frames by combining operations. The resource is well-defined.

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 implies usage for AI preparation but does not explicitly state when to use this tool versus alternatives. No when-not or prerequisite information is provided. The sibling context helps, but the description lacks explicit guidance.

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