Read an account's posts

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations by stating that the tool works without credentials and that results are ordered newest first. It also explains the filter's effect with a concrete use case. No contradictions with annotations.

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?

Three sentences with no fluff: purpose and ordering, auth requirements, and a practical filter tip. The core info is front-loaded, and every sentence earns its place.

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?

With seven parameters but 86% schema coverage and strong annotations, the description covers purpose, auth, ordering, and one key parameter behavior. The main gap is the lack of an explicit return-shape description (no output schema exists), though 'Posts by one account' gives a good indication. Slightly more detail on pagination or return format would make it fully complete.

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 high at 86%, so baseline is 3. The description adds meaningful guidance for the 'filter' parameter, recommending 'posts_no_replies' when studying how someone writes, which goes beyond the enum's generic descriptions. Other parameters are already well documented 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?

The description states a specific resource ('Posts by one account') and ordering ('newest first'), making the tool's function immediately clear. The title reinforces this, and the scoping to a single account distinguishes it from broader feed and timeline siblings like get_timline and get_feed.

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 some usage context: it works with or without credentials, and it recommends the 'posts_no_replies' filter for studying writing style. However, it never explicitly names alternative tools or states when not to use this one, leaving sibling comparison to inference.

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