Set Page Away Message

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

Annotations already cover read-only false, idempotent true, and destructive false. The description adds a useful behavioral dependency (page tokens must be loaded via meta_list_pages) and explains when the message is visible. No contradiction with annotations; it could disclose more about output/errors but is adequate for a simple setter.

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 purpose and prerequisite are front-loaded and concise. However, the Args section largely duplicates the already complete input schema, so some content does not earn its place; it is compact but not maximally efficient.

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 simple settings tool with full schema coverage and annotations, the description provides the key prerequisite and behavioral context. It does not explain output/return values, but the response_format parameter in the schema covers format selection, and no output schema makes return details less critical.

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 the baseline is 3. The description restates page_id, message, and enabled almost verbatim and omits response_format; it adds slight value by tying page_id to the prerequisite token loading, but not enough to raise above baseline.

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 uses a specific verb and resource ('Sets the away message for a Facebook Page') and adds the display condition ('shown when the page is set to away mode'). It does not explicitly contrast with sibling settings tools like meta_set_instant_reply or meta_set_greeting, so it stops short of full sibling differentiation.

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?

The description gives a clear prerequisite ('meta_list_pages called first to load page tokens') and the context of when the message applies. It does not explicitly state when not to use it or name an alternative tool, but the context and prerequisite provide clear usage guidance.

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