create_document_post

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

With no annotations, the description carries the full burden but only states the basic function. It does not disclose important behavioral traits such as required permissions, posting behavior (profile vs organization), side effects, or whether the document is uploaded or linked. This leaves the agent uninformed about key operational details.

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 overly brief for a tool with four parameters. It front-loads the primary action but lacks necessary detail. It earns a 3 as it is not wasteful but also not sufficiently informative for an agent.

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 absence of output schema and 0% schema coverage, the description is incomplete. It does not cover return values, error conditions, posting behavior, or how the parameters interact. A more thorough description is needed to compensate for the minimal schema information.

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 explain parameters. It fails to mention any of the four parameters (text, documentUrl, title, visibility) or their constraints (e.g., text max length, visibility enum). The description adds no semantic value beyond the schema structure.

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 action 'Create a post with a document' and specifies 'PDF, etc.' on LinkedIn, distinguishing it from siblings like create_text_post or create_image_post. However, it could be more precise about document types and does not differentiate from create_org_post which may also create document posts for organizations.

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 no explicit guidance on when to use this tool versus alternatives like create_image_post or create_link_post. It implies use for document sharing, but lacks context about prerequisites, limitations, or comparative recommendations for an AI agent.

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