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

Annotations declare readOnlyHint and openWorldHint, but the description adds genuinely non-structured facts: results are public-only, ordered newest-first, and include engagement counts, plus a per-call credit cost. It stops short of stating pagination semantics or how many pages are reachable.

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?

Compact and front-loaded: scope, ordering, fields and cost all land in two short sentences. The leading "User posts." fragment merely restates the title and earns nothing, a small but real waste.

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 no output schema, describing the returned counts and ordering is valuable, but for a 6-parameter tool at 50% schema coverage and no annotations covering cost or filtering, the description leaves too much to the schema. It is adequate for calling the tool, not for calling it well.

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 50%: count, cache_max_age and exclude_replies are undocumented in the schema, and the description explains none of them. "From an account" loosely gestures at handle/user_id, but a caller gets no help on page size, reply exclusion, or cache behavior — the gap the description was supposed to close.

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?

"Recent public Truths from an account, newest first, with favourite, reply and ReTruth counts" is a specific resource + scope + ordering + return-content statement. It does not, however, distinguish this from truthsocial_profile or truthsocial_post, which sit in the same family and could plausibly fetch the same content.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. truthsocial_profile for profile metadata vs this for post lists). "Costs 1 credit" is a useful budget signal but is not routing guidance, so an agent must infer selection from the tool name alone.

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