linkedin_upload_profile_photo

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

With annotations already indicating it is a mutation (readOnlyHint=false) and open-world, the description adds valuable constraints: accepted formats (JPG, PNG, GIF), size limit (8MB), and a resolution recommendation. This goes beyond the schema and annotations, though it omits details like authentication and failure behavior.

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 three short, information-dense sentences. It front-loads the primary purpose, follows with concrete constraints, and ends with a recommendation—all without extraneous content. Every sentence earns its place.

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?

For a simple one-parameter tool with no output schema, the description covers the essential aspects: purpose, accepted input constraints, and a recommendation. It does not specify return values or post-upload behavior, but for a straightforward upload operation, this is a minor gap.

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 fully describes the filePath parameter with 100% coverage, so the baseline is 3. The description adds meaning by specifying which file types and sizes are acceptable, thus enriching the semantics of the parameter beyond the schema's generic 'image file' 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?

The description clearly states the tool's function ('Upload or replace the profile photo') and specifically identifies the resource. It distinguishes from siblings like linkedin_upload_banner by explicitly targeting the profile photo, making the purpose unambiguous.

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 clear context for when to use the tool (for the profile photo) and implicitly differentiates it from the banner upload sibling. However, it does not explicitly mention alternatives or exclusionary conditions, so it falls short of a 5.

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