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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds the pagination note 'use cursor when paginated' which is useful behavioral context. However, it does not disclose rate limits, error behavior, or the structure of the returned list, so it adds moderate value beyond annotations.

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 wasted words. The core purpose is front-loaded, and the pagination hint is appended efficiently. Every sentence contributes to understanding the tool's function.

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-only list tool, the description covers the essential behavior: it lists posts, accepts a handle or account id, and mentions cursor pagination. It leaves out return structure details, but since there is no output schema and the tool is straightforward, this is a minor gap. The annotations cover safety, so the description is largely sufficient.

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 all parameters are described. The description's mention of 'by handle or account id' and 'use cursor when paginated' largely repeats the schema's own descriptions. It adds minimal new meaning, so a baseline score of 3 is appropriate given the schema already documents the parameters thoroughly.

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 clearly states the verb 'List' and the resource 'posts from a Truth Social profile', with the input qualifier 'by handle or account id'. This distinguishes it from truthsocial_profile_get (profile info) and truthsocial_post_get (single post), and the sibling list tools for other platforms are differentiated by the platform name in the tool name itself.

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 usage (list posts for a profile) but does not explicitly mention alternatives or when to choose this over truthsocial_profile_get or truthsocial_post_get. No exclusions or conditions are given, but the name and purpose make the primary use case clear. This is adequate but relies on inference.

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