Get Page Posts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only safety profile is established. The description adds the scope of 'timeline' and 'recent posts,' which provides some behavioral context. However, it does not disclose potential limitations (e.g., pagination, authorization requirements) beyond what annotations provide.

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 a single, focused sentence that conveys the core purpose without any unnecessary words. It is front-loaded with the primary action and resource.

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?

Given the tool's simplicity (2 parameters, no nested objects, output schema present) and strong annotations, the description is mostly complete. It covers the essential purpose but leaves some context implicit, such as the exact format of 'recent posts' or behavior when the page is invalid, though these are partially inferred from the output schema and tags.

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%, with both parameters clearly documented in the input schema (username example, max_posts bounds/default). The description itself does not add additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 tool's function: 'Get recent posts from a Facebook Page's timeline.' The verb 'get' identifies it as a retrieval operation, and the resource is specifically 'recent posts from a Facebook Page's timeline,' which distinguishes it from siblings like get_group_posts or get_user_posts.

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 implies usage context ('Facebook Page's timeline') and distinguishes it from other post-related tools by the word 'Page,' but it does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or alternative tool names are mentioned.

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