Upload a File (Text or Binary)

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it may create OR overwrite, overwrite defaults to false, and the endpoint is disclosed. It does not mention auth requirements or what happens on failure, keeping it short of a 5.

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?

Front-loaded with purpose, endpoint, and usage nuance before the argument list, which is easy to scan. It loses a little by restating schema field descriptions nearly verbatim in the Args block, but nothing is padded or out of order.

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 5-parameter mutation tool with no output schema, the description covers purpose, endpoint, the create-vs-overwrite behavior, the source-content exclusivity rule, and the return ("a confirmation"). Nothing an agent needs to call it correctly is missing.

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%, so baseline would be 3. However, the description adds a genuinely useful constraint absent from the schema: "provide exactly one source" for content vs contentBase64, which the flat schema with additionalProperties=false cannot express. It also clarifies filePath is relative ("figures/logo.png").

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 gives a specific verb+resource ("Upload a file to Litewrite, creating or overwriting it") and explicitly positions it against siblings: for binary assets "where edit/create are unsuitable, or as an alternative to create." An agent can route between upload_file, create_file, and write_file from the description alone.

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?

It states a clear use condition (binary assets such as images and PDFs) and names an alternative (create). There is no explicit when-not guidance, e.g. that text files should use write_file/create_file instead of this tool, so it falls short of full routing guidance.

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