Upload Image Asset

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states 'uploads' but does not mention potential side effects (e.g., whether the upload is idempotent, whether it overwrites existing assets), prerequisites (e.g., authentication, file existence), or behavior related to async operations (despite the waitForCompletion parameter). This is a significant gap for a side-effecting operation.

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 a single sentence that is front-loaded with the verb, resource, and purpose. There is no wasted wording, and every part of the sentence contributes to understanding the tool. It is appropriately sized for a straightforward upload operation.

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 four parameters, no output schema, and no annotations, the description is insufficient for an agent to fully understand the tool. It omits details on return values, parameter semantics, and side effects. While the operation is simple, the lack of structured metadata means the description should compensate but does not.

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?

The schema has 0% description coverage, and the description does not explain any parameters. Only filePath is vaguely implied by 'local image file.' The parameters name, mimeType, and waitForCompletion are completely undocumented in both the schema and the description. This is inadequate for a tool with four parameters.

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 identifies the action (upload), the resource (local image file to Canva), and the specific purpose (reusable asset for autofill image fields). It distinguishes itself from sibling tools like insert_image (which inserts into a presentation) and search_assets (which searches existing assets) by focusing on the upload-as-reusable-asset use case.

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 a clear usage context: it's for uploading a local image to be used in autofill image fields. While it doesn't explicitly mention alternatives or exclusions, the purpose statement implicitly guides the agent on when to choose this tool over siblings like insert_image or search_assets. It lacks explicit when-not-to-use guidance but is not misleading.

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