post_to_company_page

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

With no annotations provided, the description carries the full burden. It discloses a key prerequisite (LINKEDIN_ORGANIZATION_URN) and the return payload (post URN and URL), and implies permission via 'you administer.' However, it does not mention immediate visibility, publication side effects, or failure behavior, which are relevant for a write operation.

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 two tight sentences with no filler. The main action is front-loaded, followed by a clear prerequisite and return value. 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 two-parameter tool with no output schema and no annotations, the description provides the core essentials: action, target, admin scope, environmental prerequisite, and return values. It could be more complete by noting that posts are published immediately or by describing error handling, but these are minor gaps given the tool's simplicity.

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 100%, so the baseline is 3. The description itself does not add new meaning to the parameters beyond what the schema already provides for text and article_url. It mentions the overall output but not parameter-specific details.

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 states a specific verb and resource: 'Post to a LinkedIn company page you administer.' It clearly distinguishes from siblings like post_to_profile by specifying company page, and adds the admin constraint and expected return values (post URN and URL).

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 context is clear—this is for posting to a company page, not a profile—and the prerequisite LINKEDIN_ORGANIZATION_URN must be set. However, it does not explicitly mention alternatives like post_to_profile, nor does it say when not to use this tool, leaving some inference to the agent.

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