Upload a website asset

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

Describes storing asset and returning ref. Missing behavior on overwrites, size limits. Annotations (destructiveHint=false) not contradicted, but description adds limited behavioral context.

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 concise sentences with no extraneous text. Every sentence adds value.

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?

No output schema, but description explains return value. Lacks error handling and overwrite behavior, but sufficient for typical use. Good given simplicity.

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 50%; description adds context for encoding (base64/utf8) and name constraints, but project parameter remains unexplained. Adds some value beyond 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?

Clear verb 'Store' and resource 'asset under site's assets/ folder'. Differentiates from sibling list_site_assets which lists, not uploads.

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?

Implied usage: upload assets. Mentions name must be plain filename with extension, but lacks guidance on when to use this vs alternatives like upload_reference, and no prerequisites mentioned.

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