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

With no annotations, the description carries the full burden, and it discloses meaningful operational behavior: flat credit cost, free cache hits, empty results and failures never charged, and default-fresh fetching. This goes beyond the schema and gives an agent a clear sense of side effects and failure economics, though it omits potential rate limits or auth requirements.

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 is telegraphic and contains redundancy: 'Flat 1 credit. Costs 1 credit.' says the same thing twice. The opening 'One Truth' is unclear and wastes a bit of the agent's attention before the meaningful content begins.

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's list of response fields is helpful and partially compensates. However, it does not describe the overall response envelope, error conditions, or how a post ID/URL is handled, and it fails to differentiate this single-post tool from the related Truth Social list/profile tools.

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 baseline is 3, and the description mostly repeats what the schema already says about cache behavior and default freshness. It adds a little context around credit costs, but does not meaningfully explain the url parameter beyond the schema's own 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 names the resource (a single Truth Social post) by listing its data fields — text, links[], card, reblog/quote chain, media.meta, externalVideoId — but never states a verb like 'fetch' or 'retrieve'. The name and sibling tools make the purpose inferable, but the description itself is vague and cryptic ('One Truth').

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 gives no guidance on when to choose this tool over siblings such as truth_social_profile or truth_social_user_posts. It focuses on cost and caching rather than use cases, alternatives, or prerequisites. The schema's URL platform warning is useful but not usage guidance.

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