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

Annotations already declare readOnlyHint/openWorldHint/non-destructive, so the bar is lower. The description still adds distinct value: pagination via next_max_id, a trim option for lighter responses, the authentication wall for most accounts, and a cost/credit model. Credit wording is internally muddled ('at least 10 Nexscope credits' vs '1 credit per request'), which dampens the disclosure.

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 functional content is front-loaded in two useful sentences, but the text is bloated by pasted pricing boilerplate ('Actual supplier units are reported per request. Examples are not guaranteed prices.') and a redundant marketing line repeating the Trump/Vance example already given above.

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, the description compensates by listing the response fields, pagination mechanism, and the trim variant, and it flags the hard availability constraint plus cost. An agent has enough to decide eligibility and call 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 coverage is 100%, so each of the four parameters (trim, handle, user_id, next_max_id) is already documented in the schema, including the tip that user_id is faster and Trump's id example. The description restates pagination and trim at a high level without adding format or syntax detail, so baseline 3 applies.

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?

States a specific verb and resource ('Fetches a paginated list of posts from a Truth Social user') and enumerates the returned fields (text, id, created_at, url, media_attachments, card previews, reply/reblog/favourite counts). This clearly separates it from siblings social_truthsocial_post (single post) and social_truthsocial_profile (account info).

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?

Explicitly limits scope: 'Only prominent public figures (e.g., Trump, Vance) are accessible without authentication. Most other accounts require login and are unavailable.' That is a real when-not condition. It never routes to a sibling (e.g., profile lookup to obtain user_id), so it stops short of full alternative guidance.

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