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

Annotations already establish read-only and open-world behavior. The description usefully adds that only public posts are returned, that the result includes engagement counts and attached media, and that each call costs 1 credit. It still omits error behavior for deleted/private posts and any rate-limit context.

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 front-loads the key fact that this returns a single public post. The initial 'Post.' duplicates the title and adds little, but the remaining sentences are efficient.

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 simple read tool without an output schema, the description adequately explains what comes back (engagement counts and media) and the credit cost. It is incomplete on cache_max_age and does not clarify how private or deleted posts behave, leaving an agent with a couple of operational gaps.

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?

The URL parameter is well documented in the schema, but cache_max_age is undocumented in both schema and description. At 50% schema coverage, the description should compensate by explaining cache_max_age, yet it adds no parameter semantics beyond what the schema already provides.

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 a single-resource read ('A single public Truth') and distinguishes itself from list-style siblings like truthsocial_userPosts by emphasizing 'single'. However, the opening 'Post.' is just the resource name rather than a verb, and no sibling is named explicitly.

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 guidance on when to use this tool versus truthsocial_userPosts, truthsocial_profile, or other platform post tools. The only usage-adjacent note is 'Costs 1 credit,' which is cost information rather than selection guidance.

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