upload_file

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. It only states 'Uploads a file to Plone' with no mention of authentication requirements (token/cookie parameters), the need for base64 encoding, or any other behavioral traits. The agent is left completely uninformed.

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, which is concise, but it is under-specified for a tool with 7 parameters and no annotations. It lacks essential structural elements like prerequisites or parameter guidance, making it more of an under-specification than genuinely 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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is wholly inadequate. It does not explain the upload context, success/failure behavior, or how it relates to similar tools. The description appears complete only for a trivial tool, which this is not.

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 only 14% (only file_data has a description). The description adds zero parameter information, failing to explain the meaning or usage of the other 6 parameters (token, cookie, api_url, etc.). With such low schema coverage, the description was expected to compensate but did not.

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 'Uploads a file to Plone' clearly states the action (upload) and the target resource (a file to Plone). It is specific enough to understand the basic purpose, but it does not distinguish this tool from the sibling 'upload_local_asset', which may also upload files.

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 no information about when to use this tool versus alternatives, no prerequisites, and no exclusions. Given the sibling tool 'upload_local_asset', the intended usage distinction is entirely absent.

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