linkedin_profile_image

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

No annotations are provided, so the description carries the full behavioral burden. It says an upload occurs but not that an existing photo is overwritten, that authentication/session is required, what image formats/sizes are accepted, or whether the operation is reversible — all significant gaps 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?

A single, front-loaded sentence with zero filler. It is efficient, though arguably under-specified rather than optimally concise for a mutation tool.

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 write operation with no annotations, no output schema, and only 50% schema coverage, the description omits authentication requirements, overwrite behavior, and accepted file types. An agent cannot reliably call this without external assumptions.

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 50%: filePath is documented but the kind enum is not. The description's "foto de perfil o imagen de portada" does clarify the two enum meanings, adding real value, but it gives no format or path syntax detail beyond the schema.

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 ("Sube") and resource ("foto de perfil o imagen de portada"), which maps directly onto the two enum values. It is clear what the tool does, though it offers no differentiation from siblings like linkedin_profile_edit, which could also touch profile imagery.

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?

There is no guidance on when to use this versus linkedin_profile_edit or other profile-mutating siblings, no statement of prerequisites (an active session/login), and no conditions or exclusions. The agent must infer usage entirely.

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