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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds materially: the default inclusion logic (portrait + unclassified photos, all photos once none do), the captioning behavior (each image labelled with its media_id), and a firm directive to surface Retiplex URLs rather than fabricate images.

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?

Three compact sentences, front-loaded with what is returned before the workflow hint. Dense but each sentence carries a distinct payload (scope, sequencing, output/directive); minor overlap between the default-scoping clause and the actor parameter's own default description.

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?

With no output schema, the description takes on the burden of describing the return: images captioned with their media_id, which is exactly what the agent needs to chain into update_product_media. Nothing necessary for correct invocation is missing.

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 baseline would be 3, but the description adds the interaction between parameters that the schema states only per-field: the actor portrait is included by default and media_ids overrides the unclassified-photo default. That clarifies the real selection semantics beyond the field-level docs.

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 and resource ('Shows you the project's images') and immediately disambiguates scope: the actor's portrait plus every product photo still needing classifying, falling back to all photos. It is clearly distinguishable from siblings like get_project or update_product_media.

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 prescribes placement in a workflow: 'Use it before update_product_media to see which view each photo shows.' It also states the default selection rule, so the agent knows when the bare call is sufficient versus when to pass media_ids.

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