create_company_post

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

No annotations are provided, so the description carries the full burden. It mentions the admin access requirement, but this is also stated in the schema for 'profile_id'. It does not disclose whether the post is published immediately, if there are limits on content length, or what the response contains. The description adds marginal value beyond the schema but not rich behavioral context.

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 with clear front-loading of the action ('Create a post'), followed by the target ('company page') and a needed prerequisite. There is no filler or redundant information, making it concise and well-structured.

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 tool's relative simplicity (4 params, 3 required) and full schema coverage, the one-sentence description is mostly adequate. It states the tool's purpose and a key condition. However, it lacks explicit comparison to 'create_post' and provides no information about return values or failure modes, so it is not fully complete.

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?

The schema has 100% coverage, with each parameter described, including 'profile_id (must have admin access)'. The tool description adds no additional parameter semantics—it merely restates the admin requirement already present in the schema. This matches the baseline of 3 when schema coverage is high.

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 tool's action: 'Create a post on behalf of a company page'. This is a specific verb+resource combination that distinguishes it from the sibling tool 'create_post', which likely handles personal posts. The mention of admin access further clarifies the scope.

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?

It provides a clear context for use by indicating 'requires admin access', which is an important precondition. It does not explicitly name an alternative tool, but the distinction from 'create_post' is implicit in the phrase 'on behalf of a company page'. No explicit exclusionary guidance is given, so it falls short of a 5.

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