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

With no annotations provided, the description carries the behavioral disclosure burden. It does so well by disclosing pagination limits ('Up to 20 posts per page'), per-page billing ('$0.006 per page'), and the specific output fields returned. It does not cover failure behaviors or auth requirements, but for a read-style social feed endpoint this is reasonably transparent.

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 two sentences with no filler. It front-loads the core action and resource, then efficiently lists output fields and usage constraints. Every sentence contributes useful information.

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?

Given that there is no output schema, the description compensates by enumerating the returned fields and specifying pagination and cost details. It is largely complete for an agent to call correctly, though it could additionally mention rate limits or error behavior. The minimal gaps do not undermine practical use.

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 description coverage is 100%, so the input schema already fully documents all three parameters, including the @-optional username format, pagination range, and sentiment surcharge. The description adds value by restating pagination and billing, but does not introduce meaning beyond the schema parameters.

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 states a specific verb ('Get'), a clear resource ('a single Truth Social user's recent posts'), and the input method ('by username'). It also lists the returned data fields, which makes the tool's purpose unambiguous and helps distinguish it from other platform-specific user_posts siblings.

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 implies a clear use case—fetching a single user's feed by username—but does not explicitly state when to choose this tool over alternatives or when not to use it. It also does not mention any exclusions or alternative sibling tools, so usage guidance is implied rather than explicit.

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