Upload document (LinkedIn)

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

Annotations already indicate readWrite (readOnlyHint=false) and non-destructive nature. The description adds no additional behavioral disclosure beyond the schema, but does not contradict annotations.

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, which is concise, but it achieves conciseness at the cost of omitting important usage and parameter details. It front-loads the core purpose but is under-specified.

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?

With 15 parameters and an output schema available, the description fails to explain scheduling, visibility, queueing, or autogenerate features, leaving agents with insufficient context for correct usage.

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 only 53%, yet the description only explains the 'title' parameter. Critical parameters like 'user', 'documentPathOrUrl', and 'description' lack any added context, leaving agents with incomplete understanding.

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 explicitly states the verb 'Publish' and the resource 'document (PDF / PPT / PPTX / DOC / DOCX) to LinkedIn', clearly distinguishing it from sibling upload tools like upload_photos and upload_video.

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 guidance on when to use this tool versus alternatives such as upload_photos or upload_text. The only usage hint is that 'Title is required', with no context on prerequisites or exclusion criteria.

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