Get User Posts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds 'recent' and 'timeline' context, which is slightly more than the schema. However, it does not disclose any additional behavioral traits such as ordering, pagination, or potential failure modes for private accounts. With annotations present, this is acceptable but not highly informative.

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 sentence of ten words, with no redundant or unnecessary information. It is front-loaded with the action and resource, making it easy to parse quickly.

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?

The tool is simple (2 parameters), has a complete input schema, and an output schema exists. Annotations cover the read-only/open-world behavior. The description is minimal but sufficient for this simple list operation, though it could clarify the difference between 'user' and 'Page' timelines, especially given the sibling get_page_posts.

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%: both username and max_posts are fully described in the input schema. The tool description does not add any parameter-specific meaning beyond what the schema already provides, so the baseline 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 uses a specific verb ('Get') and clearly identifies the resource ('recent posts') and scope ('from a user's or Page's timeline'). This distinguishes it from sibling tools like get_group_posts, though it overlaps slightly with get_page_posts. The mention of 'recent' adds a time qualifier that matches the max_posts parameter.

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 provides no explicit guidance on when to use this tool versus alternatives like get_page_posts or search_posts. It does not mention exclusions, prerequisites, or alternative tool names. The only implied usage is that it retrieves recent timeline posts, which is not enough for effective tool selection among many similar read tools.

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