Upload or Generate Asset

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

Annotations are all false, so the description carries the behavioral disclosure burden. It reveals additional traits: AI generation costs ($0.05, $0.02/slide), large-file drop-zone behavior, and that bytes never pass through agent for large files. No contradictions. Could mention if file size limits are enforced strictly.

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 structured with a brief overall statement followed by bullet points for each purpose. It is front-loaded with the main action. While slightly lengthy, it earns its length by covering multiple use cases and edge cases without redundancy.

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 no output schema, the description covers return values (IDs) for each purpose. It addresses all 10 parameters, required fields, large-file handling, cost details, and optional chaining (pdf+translate). It is comprehensive for a complex tool.

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 100%, baseline is 3. The description adds value by explaining which parameters are required per purpose and what IDs are returned (e.g., logo_id, theme_id). It also clarifies the drop-zone behavior for large files, going beyond schema descriptions.

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: upload or generate assets (logo, theme PPTX, image, document, or AI-generated image). It lists specific purposes and their outcomes (e.g., logo_id, asset_id), distinguishing it from sibling tools like browse_catalog or plan_slide.

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 explicit guidance on when to use each purpose and for large files (>3MB) on pdf/translate/theme, it advises omitting data. It does not explicitly mention when not to use the tool vs siblings, but given no direct overlap, this is adequate.

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