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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the data source (public Mastodon-style API via residential proxy) and an explicit billing model: $0.003 USDC per successful call via x402 on Base, Solana or Arc, with failed calls uncharged. That cost and payment-rail information materially affects whether an agent should invoke the tool.

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?

Two sentences, front-loaded with the resource and its return contents before the cost/payment detail. Every clause carries information; the only mild density cost is the long enumerated field list in sentence one.

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 an output schema present, return-value explanation is unnecessary, and the description covers scope, source, and pricing. The remaining gap is error/edge behavior (private or suspended accounts, empty results), which an agent would need to interpret failures.

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; the description still adds value by clarifying that the result caps at 20 newest posts and that the payload includes profile identity fields, which contextualizes what `limit` and `replies` control. It stops short of explaining the string-typed boolean/limit quirks 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?

Names a specific resource (a Truth Social account) and enumerates exactly what is returned: profile fields plus up to 20 newest posts with text, time, engagement counts, media, link card, and repost/quote flags. The platform-specific framing makes it trivially distinguishable from social_x_com or social_instagram.

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 platform name implicitly scopes usage to Truth Social accounts, but the description never states when to prefer this over siblings like social_x_com, nor does it state prerequisites (public account, valid handle) or exclusion cases. Usage is inferable rather than prescribed.

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