truth_get_user_posts

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds the constraint that pagination IDs must be numeric, which is useful behavioral context, but it does not disclose other traits like response pagination behavior or whether posts from private accounts are excluded.

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 exceptionally concise, with two sentences that front-load the core purpose and follow with a constraint. There is no redundant or irrelevant content, 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?

Despite having an output schema, the tool has 7 parameters and no parameter descriptions. The description does not explain how to paginate using max_id/since_id, what 'pinned' means, or the effect of exclude_reblogs/exclude_replies. This leaves significant gaps for an agent to invoke the tool correctly.

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 0%, so the description must compensate by explaining parameters. It clarifies that pagination IDs must be numeric (relating to max_id and since_id) but provides no explanation for limit, pinned, exclude_reblogs, or exclude_replies. The description adds minimal meaning beyond the schema's type/default information.

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 'Fetch recent public posts for a username' uses a specific verb (fetch) and resource (public posts for a username), clearly indicating the tool's function. It distinguishes from siblings like truth_get_status or truth_home_timeline by focusing on a specific user's posts, though it does not explicitly name alternatives.

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 guidance on when to use this tool versus siblings such as truth_get_user or truth_home_timeline. The only operational note ('Pagination IDs must be numeric') is a constraint, not a usage guideline, so the tool lacks context for appropriate selection.

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