file_upload

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

No annotations are present, and the description does not disclose critical behaviors such as overwrite policies, request size limits, or error handling. The bare description 'Upload files to server' leaves the agent uninformed about consequences of invocation.

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 a single sentence with no extraneous text. However, its brevity sacrifices important details, such as clarifying the encoding parameter or the nature of the target path. It is concise but not optimally informative.

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?

With no output schema, no annotations, and 3 parameters, the description should cover usage context and return behavior. It only states the basic action, leaving gaps about success indicators, error messages, and whether the upload is synchronous.

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 is 100%, with each parameter having a functional description. The tool description adds no extra meaning beyond stating the overall action. For a 3-parameter tool with full schema coverage, 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 'Upload files to server' states a clear verb and resource, distinguishing it from sibling tools like file_list and file_delete. However, it lacks details about supported content types (text or base64) and the upload mechanism.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., kv_set for key-value storage) or on prerequisites like file size limits or authentication. The description implies use for file uploads but offers no context for decision-making.

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