Upload Photo

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

Discloses important behaior beyond what annotations provide: re-encoding via WebP, stripping EXIF/AI metadata, person uploads writing to the CRM gallery and avatar, plus pricing and API-key requirement. This gives the agent clear expectations about side effects before invoking the tool.

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?

Three dense sentences cover the action, input constraint, transformation behavior, side effects, cost, and auth requirement without wasted words. The primary purpose is front-loaded and every sentence adds value.

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 output schema exists and the annotations already indicate this is a read-write operation, the description supplies the missing behavioral, side-effect, cost, and auth context. The agent has everything it needs to decide whether and how to call this 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?

The schema already documents most parameters, and the description reinforces the key constraint that exactly one of image_base64 or url is required. It also adds meaning for set_as_avatar by explaining the avatar side effect, which is not present in the schema property description.

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?

States a specific verb and resource: upload a photo to a Life Graph entity. The description clearly establishes this as a photo-specific upload distinct from generic sibling tools like upload_asset, and adds meaningful scope by noting person-gallery behavior.

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?

Cleary states the main use case and the two acceptable input modes (image_base64 or url, one required). It also explains the person-upload side effect, giving an agent relevant context, though it does not explicitly name alternative sibling tools or state when not to use this tool.

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