Create company post

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

Annotations already indicate readOnlyHint=false and openWorldHint=true, and the description's 'publish' aligns with these. It adds that the post is a text post destined for a company page, but does not disclose additional behaviors such as moderation, error conditions, or immediate visibility.

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 concise sentence that immediately conveys the core action. No wasted words or redundant information.

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 simple create operation, full schema parameter descriptions, and the presence of an output schema, the description is minimally sufficient. However, it lacks context about how this differs from company_schedule_post and does not mention any side effects or prerequisites beyond what annotations provide.

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?

All four parameters have descriptions in the schema (100% coverage), so the description does not need to explain them. It does not add any parameter-specific context beyond what the schema already provides.

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 uses the specific verb 'publish' and identifies the resource as 'a text post to the company page'. This clearly differentiates it from sibling tools like company_edit_post, company_delete_post, and company_schedule_post, which have distinct actions.

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 implies this tool is for immediately publishing a text post, but it does not explicitly contrast with company_schedule_post or other alternatives. No exclusions or alternative recommendations are provided, leaving the agent to infer usage based on the tool's name.

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