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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false. The description adds useful behavioral context beyond annotations: the 20-posts-per-page limit, per-page billing, and the fields returned. It stops short of covering auth, rate limits, or error behavior, but it is strong for a read-only social feed 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?

Three sentences, front-loaded with purpose, then return payload, then pagination and billing. Every sentence adds value with no redundancy or filler.

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 read-only paginated fetch with no output schema, the description supplies the missing return-value summary and important cost/pagination details. Annotations cover the safety profile and the input schema covers parameters, so the definition is complete enough to invoke 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 description coverage is 100%, so username, pages, and get_sentiment are already well documented. The description adds billing per page and repeats the page size, but it does not add syntax or meaning for the parameters beyond what the schema provides. Baseline 3 is appropriate.

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 ('Get a Truth Social user's recent posts (their feed) by username') and names the platform explicitly. It clearly distinguishes this from generic search tools or user-post tools for other social networks.

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?

Gives clear context for use: when you have a Truth Social username and need that user's recent feed. It does not explicitly name when-not-to-use cases or alternatives, but the platform-specific scope and lack of sibling Truth Social tools make the intended use unambiguous.

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