Get recent media from connected accounts

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, signaling a safe read operation. The description adds that media is 'pulled directly from a profile's connected social accounts,' implying live fetching but omitting potential rate limits or real-time behavior. This adds minimal behavioral detail beyond 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?

Two sentences efficiently convey purpose, scope, and utility. No redundant words or unnecessary details.

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?

The description covers the tool's core function and platform support. With an output schema present, return value explanation is not needed. However, the limit parameter lacks description in both schema and description, and pagination behavior is not addressed. For a straightforward read tool, this is adequate but 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?

Schema description coverage is 75% (3 of 4 parameters documented). The description adds value by listing supported platforms (e.g., instagram, tiktok), which expands on the platform parameter's schema description. However, it does not clarify the limit parameter's behavior or pagination, and the user and page_urn parameters are already well-described in the schema.

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 the verb 'retrieve recent media' and specifies the resource 'from a profile's connected social accounts', listing supported platforms. This distinguishes it from sibling tools like get_media_upload (upload status) and other get_* 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?

The description says it is 'useful for browsing what already exists on a platform before posting more,' which provides clear context. However, it lacks explicit guidance on when not to use this tool or alternatives, such as sibling tools for analytics or specific platform data.

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