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

Annotations already mark this as destructive and open-world, and the description adds valuable context: publishing cannot be undone from here, it schedules to connected accounts, and it fails if the post is unfinished or no account is connected. It also clarifies the owner-authorization prerequisite.

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 usage condition is front-loaded, followed by the effect, irreversibility, and operational limits. Every sentence carries useful information with no filler.

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 two-parameter mutation with destructive and open-world annotations and no output schema, the description covers prerequisites, effect, irreversibility, and failure modes. It could still say more about what a successful call returns, but it is largely 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?

Schema description coverage is 100%, so postId and the when enum are already well documented. The description reinforces 'one specific post' and the now versus its_day behavior, but adds no syntax or meaning beyond 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?

States a specific verb and resource: approving/posting one specific post, with the effect of scheduling it to connected social accounts. It does not explicitly differentiate itself from siblings such as get_my_posts or best_time_to_post, so it falls short of a 5.

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?

Gives an explicit usage gate: only when the signed-in owner has clearly said to approve or post one specific post after seeing it. It also states one-post-per-call and failure conditions, but does not name alternative tools for finding or preparing a post.

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