tokportal_upload_image_direct

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

The description adds the specific behavior that HEIF/HEIC files may be converted to JPEG, which is beyond the annotations. However, it omits other behavioral traits such as whether uploads are synchronous, whether existing files are overwritten, or any authentication or file size constraints. With sparse annotations (no readOnlyHint or destructiveHint), the description carries moderate burden but provides minimal additional context.

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 extremely concise: two sentences that deliver the core purpose and a critical behavioral note. Every word earns its place, with no redundancy or filler. It is front-loaded with the main action.

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 there is no output schema, the description mentions 'returns storage details' but does not specify what those details are (e.g., URL, ID, dimensions). It also lacks constraints like max file size or accepted formats beyond the HEIF note. For a tool with four parameters and no output schema, the description is somewhat incomplete.

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 all four parameters are already described in the schema. The description only adds that the upload is multipart/form-data, which is implied by the schema's parameter names. No meaning is added beyond what the schema provides, so baseline score of 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 verb 'Upload', the resource 'image file', and the method 'multipart/form-data directly through TokPortal'. It also mentions a key behavioral detail about HEIF/HEIC conversion, distinguishing it from sibling tools like tokportal_upload_image_from_url. The title reinforces this purpose.

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 does not provide any guidance on when to use this tool versus the alternative upload tools (e.g., tokportal_upload_image, tokportal_upload_image_from_url). It only says 'directly' but lacks explicit when-to-use or when-not-to-use advice. Given the large sibling list with similar upload functions, this omission is significant.

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