Post to a Page

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

Beyond the sparse annotations, the description explains the three posting behaviors (immediate, draft, scheduled) and that publishing is the default. It doesn't mention Page-access requirements or external visibility consequences, but the core side effect—creating and publishing a post—is plainly disclosed. No contradiction with 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?

Three short sentences, front-loaded with the core action, then conditional behavior. No filler or repetition of schema text.

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 5-parameter creation tool with no output schema and all parameters documented, the description covers the relevant decision points. It lacks explicit mention of permissions or response semantics, but those are common to this domain and can be inferred from the resource being created.

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?

With 100% schema coverage the baseline is 3, and the description earns extra credit by explaining the relationship between publish_at and draft ('Leave publish_at empty and draft false to post immediately'). It also clarifies that link is an optional attachment, which aligns with the schema.

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 opens with 'Publish a text post, optionally with a link,' giving a specific verb, resource, and scope. This clearly distinguishes it from the sibling create_photo_post and from update/delete operations.

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 gives clear operational guidance for the main modes: leave publish_at empty and draft false for immediate posting, set draft to keep unpublished, or set publish_at to schedule. It does not explicitly call out alternatives like create_photo_post, but the 'text post' phrase implies the boundary, so the guidance is clear though not exhaustive.

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