Send Page Message

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

The description confirms a write operation (sends a message) consistent with readOnlyHint=false. It adds specific behavioral constraints (24-hour window, permission) beyond annotations. No contradictions.

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?

Extremely concise: one paragraph with clear bullet-like args. Every sentence adds value (purpose, args, permission, window). No fluff.

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?

Covers purpose, parameters, requirements, and limitations. No output schema needed. Could mention idempotency or response format, but not critical for this simple tool.

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 low (33%), so the description compensates by listing parameters with brief explanations (e.g., 'PSID' for recipient_id). However, it lacks details like minLength for message or format hints, leaving some gaps.

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 clearly states the action (sends a message), the resource (from a Facebook Page to a user), and the context (in an existing conversation). It distinguishes from siblings like meta_send_instagram_message by specifying 'Facebook Page' and 'existing conversation'.

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 mentions the 24-hour messaging window restriction and required pages_messaging permission, providing clear context for when to use. It does not explicitly mention when not to use or alternatives, but the constraints are well-articulated.

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