Upload a file to Wiro

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

Annotations already convey that this is a mutating operation (readOnlyHint=false) and may access external resources (openWorldHint=true). The description adds the nuance that the file must be 'remotely accessible' and becomes 'Wiro-hosted,' but it does not disclose potential side effects like data transfer implications, storage limits, or irreversibility. This is reasonable given the annotations but leaves some behavioral detail unstated.

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 two sentences, front-loaded with the core purpose and followed by a practical usage note. Every sentence earns its place with no redundancy or filler.

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 tool with a 2-parameter schema, full parameter descriptions, and an output schema (implied by context), the description covers the essential purpose, usage boundaries, and key caveat. It lacks nothing critical for an agent to decide when and how to invoke it.

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 input schema fully documents both parameters with 100% coverage, so the description does not need to explain them. The description adds minimal semantic context ('remotely accessible' relates to the url parameter), but the schema descriptions already are clear. 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 tool uploads a remotely accessible file to Wiro, with a specific verb and resource. It further distinguishes itself from sibling tools by noting that most models accept source URLs directly, making the purpose and scope unmistakable.

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 explicit when-to-use guidance: 'use this only when the model schema requires a Wiro-hosted file or the same file will be reused.' It also implies an alternative (direct source URLs), which helps the agent decide between this tool and other model invocation flows.

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