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

With no annotations provided, the description carries the burden of behavioral disclosure, and it does well: it states the 2-credit cost, that empty results and failures are never charged, and that cache=true gives a free 24-hour cache hit while the default is always fresh. This goes beyond basic operation and helps the agent anticipate cost and caching behavior.

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 short and mostly front-loaded, but it contains a clear redundancy: '2 credits. Costs 2 credits.' The phrase 'same post mapper as /post' is compact but leaves the reader to infer what that mapper fully entails.

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?

There is no output schema, so the description should explain return behavior; it references the '/post' mapper but does not self-containedly describe the response structure. It compensates with cost, caching, and failure/charing details, but an agent still needs to look elsewhere to understand the exact response shape.

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 100%, so the parameters are already documented, including the url platform-matching requirement, pagination via cursor, and the 80-post cap. The description adds little beyond what the schema states; the cache explanation merely restates the schema's cache parameter description.

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 identifies the resource as a user's recent Truths and clarifies the post mapper behavior (links, card, reblog/quote, mentions). It is clearly distinct from sibling tools like truth_social_post and truth_social_profile, though it relies on the plural 'Truths' and tool name rather than an explicit verb like 'list' or 'fetch'.

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 guidance on when to choose this tool over truth_social_post, truth_social_profile, or other platform user-post tools. The description mentions '/post' for output mapping but does not instruct an agent on selection criteria such as needing recent posts vs. a single post or profile details.

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