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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful output context ('Thumbnails are attached') but does not disclose pagination behavior for limit/offset, so it adds only modest value beyond the structured fields.

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 tight sentences, front-loaded with the action and resource, with parenthetical asset types and a note on thumbnails. No wasted wording.

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 read-only listing tool with annotations carrying the safety profile and no output schema, the description covers scope, asset types, and the thumbnail return detail. The only gap is implicit pagination via undocumented limit/offset, which is minor for a straightforward list operation.

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 50%: influencerId and role are documented in the schema (role with example values like static_ugc, carousel_slide, character_sheet), while limit and offset are not. The description only restates the optional role filter and adds no syntax or pagination semantics, so it does not compensate for the coverage 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?

States a specific verb (List) and resource (generated assets in an influencer's vault), and enumerates the asset kinds (portraits, stills, b-roll, video clips), which lets an agent distinguish it from siblings like list_influencer_studio_images. It does not explicitly name which sibling to prefer, keeping it just short of a 5.

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 only usage guidance is 'Optionally filter by role,' which implies the role parameter is optional but gives no when-to-use/when-not framing or alternatives against the many sibling list_* tools. Usage is implied rather than stated.

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