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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description usefully adds the auth restriction and the media-download side effect (permanent Supabase URLs). But the cost disclosure is internally contradictory: "at least 10 Nexscope credits", "1 credit per request", and "Costs 10 credits if media is found, 1 credit otherwise" cannot all be true, leaving the agent unable to predict spend.

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 definition contains pasted-in pricing-page cruft ("Truth Social Post API View Pricing Get Truth Social post 1 credit per request") and repeats the download_media explanation verbatim from the schema. The conflicting credit figures force the reader to reconcile three different numbers.

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 two-parameter read tool with no output schema, listing return fields and the auth gate is genuinely helpful. Still missing: how to handle a post that isn't from a public figure (error vs empty), and a coherent cost statement an agent could use to decide whether to enable download_media.

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% and download_media's schema description already explains the Supabase URL return and credit costs, so the description adds no new parameter meaning. Baseline 3 applies; the duplicated download_media sentence is redundant rather than additive.

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 first sentence gives a specific verb and resource ("Fetches a single Truth Social post by URL") and enumerates the returned fields, so an agent can distinguish it from social_truthsocial_user_posts and social_truthsocial_profile at a glance.

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 implies the usage context (single post, given a URL) and adds a real eligibility constraint ("Only posts from prominent public figures ... are accessible without authentication"). However, it never routes the agent to the sibling tools for multi-post or profile retrieval, and never states when not to use this tool.

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