images_upload

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

MIME auto-detection is disclosed, but no mention of destructive behavior, rate limits, or authentication needs. With no annotations, the description provides only basic behavioral info.

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 sentences with front-loaded purpose. Efficient, but could be more structured with bullet points for clarity.

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?

Missing critical context: editId dependency, no output description, and no linkage to sibling tools like edits_insert. Incomplete for a 5-param mutation tool.

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 80%, but the description only repeats the schema's 'file' path hint and adds MIME info, which is behavioral rather than semantic. No explanation of imageType enum, packageName, or editId.

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 'Upload a new image', with a specific verb and resource. It differentiates from sibling tools like images_delete and images_list by focusing on upload.

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 on when to use this tool vs alternatives, or prerequisites such as needing an editId from edits_insert. The required parameters are not explained in context of the workflow.

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