upload_asset

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

No annotations provided, so description carries burden. It mentions MIME validation and storage path via block_type, but does not disclose file size limits, overwrite behavior, permissions, or error handling. Moderate disclosure.

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?

One well-organized paragraph front-loading the action and use cases. Efficient but could be slightly more concise; still no wasted sentences.

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 9 parameters and no output schema, description adequately explains when and what to upload, and parameter semantics via examples. Lacks details on response behavior but sufficient for selection and invocation.

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 descriptions cover all 9 parameters (100% coverage). The tool description adds value by listing accepted file types per block_type (e.g., 'logos (SVG/PNG/JPG)'), which is not in schema.

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 'Upload a file from the local filesystem into a block in BrandKity' and lists specific use cases (logos, visuals, etc.), distinguishing from sibling tool upload_file for fonts.

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?

Explicitly states when to use (logos, visuals, etc.) and when not to (fonts, with alternative 'use upload_file → add_typography(asset_url) instead').

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