Get Visitor Posts

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

Annotations already indicate readOnlyHint=true, so read-only behavior is clear. Description adds no further behavioral details (e.g., pagination with 'after' parameter, response format options, or rate limit considerations).

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 short, but lacks essential information. Could be considered concise, but the omission of important parameters and context reduces effectiveness.

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?

Incomplete coverage of parameters and no usage context. The description does not fully inform the agent about the tool's capabilities, given the 4-parameter schema and no output schema to compensate.

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?

Only describes 2 of 4 parameters (page_id, limit). The 'after' and 'response_format' parameters are missing from the description, providing incomplete semantic guidance despite their presence in 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?

Clearly states it retrieves visitor posts from a Facebook Page wall. However, it does not explicitly differentiate from similar sibling tools like 'meta_get_published_posts' or 'meta_get_posts', but the focus on 'visitor' posts provides sufficient specificity.

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 on when to use this tool versus alternatives such as 'meta_get_posts' for all posts. No prerequisites or context about required permissions (e.g., page access token).

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