asset_ingest_external

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

The description outlines the pipeline steps but lacks details on side effects, permissions, what happens to the input image, or output format. Annotations are minimal, so description should compensate but does not.

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 sentences, concise and front-loaded, but could better structure the pipeline steps and parameter context.

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?

With 7 parameters, low schema coverage, no output schema, and a multi-step pipeline, the description is incomplete. It omits parameter semantics and does not explain 'tier-0 validation' or output.

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 only 14%, and the description adds no parameter explanations beyond the pipeline mention. It does not describe brand_bundle, expected_text, vector, transparent, or output_dir.

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 ingests externally generated images and runs a specific pipeline (matte, vectorize, validation), distinguishing it from sibling generation tools.

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 provides context by listing external tools and mentioning 'round-trip endpoint for external_prompt_only mode', but does not explicitly state when not to use it or name alternatives.

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