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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the result is 'one post with its stats and author' and that it accepts 'any public URL,' which is useful. It does not mention read-only behavior, error cases, authentication needs, rate limits, or what happens when a user/profile identifier is supplied, leaving meaningful gaps.

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 structure is front-loaded with the core purpose and then proceeds through a dense, platform-by-platform list of accepted forms. The repeated 'username or profile URL; for posts…' pattern adds length and ambiguity, but each sentence carries concrete parameter value rather than 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?

Given no annotations, no output schema, and 0% parameter schema coverage, the description does a strong job of covering the two parameters and the expected output ('stats and author'). It is still missing output structure, error semantics, and clarification of why username/profile forms appear in a post-fetching tool, so it is not fully complete.

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 input schema has 0% description coverage and only bare 'platform' and 'id' string fields. The description compensates thoroughly by enumerating accepted identifiers per platform, including shortcodes, activity ids, t3_ ids, handles, and URL patterns, giving an agent the concrete format guidance needed to supply valid 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 opens with 'One post with its stats and author,' which clearly states the verb, resource, and scope, distinguishing it from siblings like get_user_posts and get_comments. However, the per-platform list includes 'username or profile URL' forms, which confuses whether this tool also accepts user identifiers, so it is not fully unambiguous.

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 gives extensive accepted id/URL formats for each platform, such as 'a shortcode or /p/ or /reel/ URL' for Instagram and 'a tweet id or status URL' for X. It does not explicitly say when to prefer get_post over alternatives like get_user, get_user_posts, or search, nor does it state exclusions, 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.