upload_profile_photo

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

No annotations are provided, so the description carries the full burden. It discloses that browser automation is required, which is a key behavioral trait. However, it lacks details on permissions needed, whether the upload overwrites existing photos, rate limits, or error handling. The description adds some value but is incomplete for a mutation 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?

The description is front-loaded with the core purpose, followed by prerequisites and parameter details in a structured format. Every sentence adds value: the first states the action, the second specifies requirements, and the third explains the parameter and return. There is no wasted text.

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 that this is a mutation tool with no annotations, 1 parameter, and an output schema (implied by 'Returns success status'), the description is fairly complete. It covers the purpose, prerequisites, parameter semantics, and return indication. However, it could improve by detailing behavioral aspects like overwrite behavior or error cases.

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 0%, so the description must compensate. It adds meaning by specifying that 'photo_path' is an 'Absolute path to the photo file (JPG, PNG)', clarifying the parameter's purpose, format, and allowed file types. This goes beyond the schema's basic type definition. However, it does not cover edge cases like file size limits.

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 specific action ('Upload a new profile photo') with the resource ('profile photo'). It distinguishes itself from sibling tools like 'upload_background_photo' by specifying the target resource, and from other profile-related tools (e.g., 'update_profile_headline', 'update_profile_summary') by focusing on photo 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?

The description provides explicit context for when to use this tool: 'Requires Playwright browser automation to be enabled.' This is a clear prerequisite. However, it does not mention when not to use it or name alternatives (e.g., using 'update_profile_headline' for text updates instead).

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