Create Photo Post

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false, so the write/external-facing profile is covered. The description adds that publishing can be deferred via scheduling, which is real context beyond the annotations. It omits any auth/permission requirement and does not say what happens when both or neither image source is supplied, which matters because zero parameters are required.

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?

A single front-loaded sentence with the action first and the two source modes after; every clause carries information and there is nothing to trim.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return values. The one meaningful gap is the required-input ambiguity: no parameter is marked required, yet the description implies an image source is needed, without stating it. Otherwise sufficient for correct invocation.

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 coverage is 80%, so the schema carries most parameter meaning (including the scheduling window and Page default). The description only restates the image_url vs image_path choice that the schema already documents, adding no new syntax, constraints, or defaults. Baseline 3 applies.

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 ('Publish (or schedule)') and a specific resource ('photo post'), and the qualifier 'photo' implicitly separates it from create_post and create_reel in the sibling list. It stops short of naming an alternative explicitly, so the differentiation is inferred rather than declared.

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?

'(or schedule)' and 'from a public URL or a local image file' hint at two usage modes and two source options, which is useful implied guidance. However, there is no explicit statement of when to pick this over create_post or create_reel, no prerequisite (Page permissions/admin role), and no note that the two image sources are mutually exclusive.

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