Uploads an image.

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

Annotations include 'openWorldHint: true' indicating potential side effects, but the description only says 'Upload image of the pet.' with no details on behavioral traits like overwriting, file size limits, authentication needs, or what happens on success/failure. Minimal disclosure.

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 ('Upload image of the pet.') and is front-loaded. However, it is too brief and omits essential information, making it less effective despite its conciseness.

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 complexity of a file upload tool with side effects (openWorldHint), the description is severely incomplete. No information about file type, size, return value, or how to provide the image. The missing output schema exacerbates the lack of context.

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?

The input schema lacks a file parameter, which is critical for an upload tool. The description does not clarify how the image is provided (e.g., multipart form data, base64). Although both parameters (petId, additionalMetadata) have schema descriptions, the absence of a file field is a major omission that the description should address.

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 states 'Upload image of the pet.' which clearly indicates the action and resource. It distinguishes from sibling tools like 'update_pet' which focus on updating general pet info, though the title is slightly inconsistent ('Uploads an image.' vs 'Upload image of the pet'). Overall clear 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?

No explicit guidance on when to use this tool vs alternatives like 'update_pet' or 'add_pet'. No mention of prerequisites, file requirements, or context. The agent is left guessing when to invoke this tool.

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