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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true), and the description usefully adds two behavioral facts annotations cannot carry: the authentication restriction on which accounts resolve, and that lookups consume Nexscope credits with possible re-purchase on repeats. However, the cost disclosure contradicts itself — 'at least 10 Nexscope credits' versus '1 credit per request' — and the appended supplier boilerplate makes the true pricing ambiguous, which matters for a metered 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?

The first two sentences are well front-loaded and earn their place, but the tail is pasted marketing copy ('Truth Social Profile API View Pricing Get Truth Social profile info 1 credit per request... Examples are not guaranteed prices') that duplicates the cost statement and introduces a numeric conflict. Roughly half the text is boilerplate rather than tool guidance.

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?

For a one-parameter read tool with no output schema, the definition covers the essentials: what fields return, which accounts resolve, and that calls are metered. It is weakened by the unresolved pricing contradiction and by not saying whether a failed lookup (a non-public-figure handle) still incurs credits.

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?

There is a single parameter with 100% schema description coverage ('Truth Social username'), so the schema baseline of 3 applies. The description adds no format guidance — whether the handle takes an '@' prefix, is case-sensitive, or whether a display name is accepted — so it does not go beyond 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?

The opening sentence gives a specific verb and resource ('Retrieves a Truth Social user's public profile') and enumerates the returned fields, so an agent knows exactly what data comes back. It does not explicitly distinguish itself from the sibling tools social_truthsocial_post and social_truthsocial_user_posts, leaving that separation to inference.

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?

It states a critical applicability constraint: only prominent public figures are accessible unauthenticated and 'most other accounts will not work.' That is real when-to-use guidance beyond a generic description. It stops short of naming alternatives (e.g., social_find_social_profiles or the other Truth Social endpoints) or saying what to do when a handle is not a public figure.

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