Get a post

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

Beyond the read-only, idempotent, open-world annotations, it discloses the cost of one credit per call, free failures, and free cached repeats when using max_age_days. These billing and caching details are valuable operational context and do not contradict the 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 front-loads the retrieval scope and returned fields, then compactly covers pricing and alternative routing. The exhaustive platform list duplicates the schema enum and creates unnecessary bulk in the middle.

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 normal platform-and-URL call, it covers the purpose, result content, supported platforms, cost, and fallback tools, which is sufficient despite the absence of an output schema. It would be more complete if it clarified when id replaces url and how max_age_days controls caching or freshness.

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 the schema already documents platform, url, id, and params; the description's URL wording and platform enumeration add little beyond that. Mentioning max_age_days is useful, but the description does not explain where it is supplied, its default, or its valid values.

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 precisely states that the tool retrieves one post, video, tweet, pin, or clip by URL and identifies the returned content as text, author, stats, and media. The final sentence also distinguishes it from the platform-specific sibling tools.

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 defines the appropriate use case as single-item retrieval on a supported platform and explicitly directs broader needs to the platform's own tool. Although that boundary is general, both the when-to-use context and an alternative are explicit.

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