upload_asset

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

With no annotations and a minimal description, the behavioral transparency is extremely poor. The description does not disclose that this tool creates a new asset, requires a file upload, or any side effects or permissions needed.

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 overly terse at one short sentence, lacking sufficient content to be useful. While concise, it fails to earn its place by not conveying essential information.

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 complexity (5 parameters, nested file object, no output schema, no annotations), the description is wholly incomplete. It does not cover return values, side effects, or usage context among siblings.

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 low at 40%, and the description adds no parameter meaning beyond the schema. The description fails to explain the nested 'file' object with its required sub-properties, nor does it clarify 'title' or 'description'.

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 'Upload a new asset' clearly identifies the action (upload) and resource (asset), distinguishing it from sibling tools like delete_asset, update_asset, and get_asset. However, it could be more specific about the file upload context.

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 no guidance on when to use this tool versus alternatives like update_asset, nor does it mention prerequisites such as space and environment IDs. There is no indication of when not to use it.

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