get_v2_media_info_by_url

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

Discloses key behaviors: returns 200/404 for specific cases, lacks usertags for video, and promoted posts may 404. Without annotations, this is valuable, though auth constraints or rate limits are omitted.

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?

Description is somewhat verbose with repeated notes and a redundant final line. While structured with line breaks, it could be trimmed for conciseness.

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 single-parameter tool, the description covers purpose, usage, behavior, and parameter format. The lack of output structure is a minor gap given no output schema.

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 schema has 0% coverage, but the description provides a concrete URL example ('https://ins...ram.com/p/CA2aJYrg6cZ/'), clarifying expected format. This compensates well for the schema gap.

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 it retrieves media info by URL. It specifies the resource ('media object') and distinguishes from siblings by noting alternatives for promoted posts and other ID-based 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?

Explicitly mentions when to use (for standard posts) and when not to (for promoted/ad posts, use /v2/media/by/url). Provides URL format guidance, aiding correct tool selection.

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