Set Page Messenger Greeting

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

Beyond annotations (idempotentHint=true), the description only adds that the text is shown before first message. It does not mention side effects, overwriting behavior, or authorization needs, leaving significant behavioral gaps.

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 clear sentences plus an arg list, front-loaded with purpose. Efficient with no waste, though the arg list duplicates schema content.

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?

Simple tool with annotations, but description omits response_format handling and error conditions. Prerequisite is noted, but overall completeness is adequate for a straightforward setter.

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 100%, but description merely restates schema descriptions for page_id and greeting_text, adding no new meaning. The optional response_format parameter is not mentioned in the description, failing to add value.

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 it sets the Messenger greeting text for a Facebook Page, specifying it's shown before first message. Does not differentiate from sibling tools like meta_set_away_message or meta_set_instant_reply, but the action is unambiguous.

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?

Explicitly requires calling meta_list_pages first to load page tokens, which is good context. However, no guidance on when to use this vs alternative set tools, nor conditions when not to use.

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