Get Broadcast Channel Messages

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that it returns paginated results via the 'after' parameter, but does not disclose other behaviors like error handling, rate limits, or response format variants. With annotations covering safety, the description adds minimal extra context.

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 description is extremely concise: one sentence for the action, a structured list of arguments, and a return description. Every sentence serves a purpose with no redundancy. The most critical information is front-loaded.

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 read-only tool with annotations and high schema coverage, the description covers the main functionality. However, it omits the response_format parameter, which is important for output control, and does not explain pagination behavior beyond the 'after' parameter. Slightly incomplete for a tool with 4 parameters and no output schema.

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 75% (3 of 4 parameters described in schema). The description repeats the schema's parameter descriptions for channel_id, limit, and after, but omits the response_format parameter entirely. Since schema coverage is high, baseline is 3; the description adds no new semantic information 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?

The description clearly states 'Gets messages in an Instagram broadcast channel', specifying the verb and resource. It distinguishes from sibling tools like meta_get_instagram_broadcast_channels (which retrieves channels) and meta_send_broadcast_channel_message (which sends messages).

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites (like channel ownership or permissions), or any limitations. The description is purely functional and offers no contextual usage advice.

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