Upload a file

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

With only openWorldHint in the annotations, the description carries most of the burden: it discloses the return value (file id) and the crucial behavioral fact that the upload is unlinked to any ticket, which dictates downstream flow. It does not mention permissions, size limits, or overwrite behavior for same-named files, so it is strong rather than complete.

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 tightly written sentences with zero filler; the purpose and the follow-up routing are both front-loaded and every clause earns its place.

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?

Despite having no output schema, the description explains what is returned (file id) and how it should be used next. For a two-parameter, single-required upload tool this covers everything an agent needs to invoke it correctly.

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 description coverage is 100%, so both filePath and fileName are already documented in the schema with their defaults and format ('absolute path', default name). The description adds no additional parameter meaning, making the baseline 3 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?

Specific verb+resource+outcome: 'Upload a local file into the file manager of the site and return its file id.' It is clearly distinguishable from siblings like download_attachment and add_ticket_attachments, and the return value is stated up front.

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 the post-upload state ('The file is not linked to a ticket yet') and routes the agent to the correct next tools ('pass the id to add_ticket_attachments or to create_ticket'). This is exactly the when-to-use/alternatives guidance the dimension asks for.

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