Post as a Page

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

Annotations indicate readOnlyHint=false, so the tool is known to be a write operation. The description adds the admin requirement and page source from list_pages, but doesn't discuss side effects, visibility, or failure modes. This is moderate value beyond 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?

Two sentences, front-loaded with purpose, then a helpful pointer to list_pages. No wasted words.

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 two-parameter action, the description is quite complete: it covers prerequisite (being admin), parameter source, and action. The lack of output schema means return value isn't specified, but that's acceptable for low complexity.

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 description repeats the schema's page description and implies text is the post content, but doesn't explicitly define text beyond the schema constraints. With 50% schema coverage, the description partially compensates but doesn't fully clarify text semantics.

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?

Clearly states the tool publishes a text post as a Company/showcase Page, distinguishing it from sibling tools like create_post and schedule_post. The verb 'publish' and resource 'Page' are specific.

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?

Provides context that it applies to Pages the user administers and directs to list_pages for valid page identifiers. While it doesn't explicitly name alternatives, the distinction from create_post (likely for personal posts) is clear from the title and description.

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