get_v1_media_by_id

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention any side effects, authentication requirements, rate limits, or what the response contains. The description adds no behavioral context beyond the endpoint path.

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 is extremely short, but this is due to under-specification rather than conciseness. It fails to earn its place by conveying essential details, instead merely repeating the tool name and method.

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 the moderate complexity (multiple similar siblings, one parameter, no output schema), the description is drastically incomplete. It does not clarify the output structure, how it differs from get_v1_media_by_url, or what 'Media' refers to (e.g., a TikTok video, image, etc.).

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 0%, yet the tool description provides no additional meaning for the 'id' parameter. The parameter pattern (^\d{19}$) implies a numeric ID format, but the description does not confirm this or explain what the ID represents.

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 'Media By Id' is a tautology that restates the tool name without specifying what action is performed or what type of media is retrieved. It does not distinguish this tool from siblings like get_v1_media_by_url or get_v1_media_comments_by_id.

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?

No guidance is provided on when to use this tool instead of alternatives. The description fails to mention that this tool fetches a single media object by its numeric ID, nor does it explain scenarios where other tools (e.g., get_v1_media_by_url) would be more appropriate.

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