upload_file

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

Annotations already indicate idempotentHint=true, but the description adds the specific 24-hour reuse window and that it returns a hosted URL. This goes beyond the annotations by explaining the dedup behavior and the return value, though it doesn't detail side effects beyond the upload. No contradiction with annotations.

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 sentences, front-loaded with the core action and purpose. The second sentence provides usage guidance. Every word earns its place, with no redundancy or fluff. Perfectly concise.

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?

For a simple one-parameter tool with no output schema, the description covers the purpose, the return value (hosted URL), the dedup behavior, and the typical usage context relative to siblings. It's fully self-sufficient without needing additional details.

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 single parameter 'path' is already described in the schema with 'Local file path.' The description adds no additional semantic information about the path format, restrictions, or how it relates to the '@./path' convention. Since schema coverage is 100% and there's only one simple parameter, a baseline 3 is appropriate.

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 action: 'Upload a local file to WaveSpeed and get its hosted URL.' It also mentions the deduplication behavior (identical bytes reuse the same upload) and distinguishes itself from run_model, which handles the same input natively. This is a specific verb+resource with clear scope.

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 this tool is usually unnecessary and gives the alternative: 'Usually unnecessary — run_model handles '@./path' inputs itself.' This is direct when-not-to-use guidance with a named alternative, making it exceptionally clear for the agent.

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