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

Annotations mark this as a non-readonly but idempotent, non-destructive write; the description adds the crucial behavioral semantics annotations cannot carry — that passing all:true constitutes the owner's rights representation, that it mirrors approve_post, and that the agent must not confirm on its own judgment. It also discloses the list-vs-mutate behavior and the downstream effect on AI-art usage.

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 tight sentences front-load the what, then the how-to-call, then the critical caution, in descending order of urgency. Every sentence carries actionable content with no filler.

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 four-parameter, dual-mode tool with no output schema, the description covers both primary paths and the rights constraint well. It omits any reference to the collections/facts grouping capability, relying entirely on the schema for that, and only loosely implies the shape of the returned list.

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 is 3. The description adds genuine operational meaning beyond the schema by clarifying that 'neither assetIds nor all' triggers a pure list call and by emphasizing the rights weight of all:true, though it never mentions the collections parameter.

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 states a specific dual-mode purpose: listing unconfirmed candidate photos crawled from the brand's site, or confirming them into the image library so posts use real photos instead of AI art. The verb+resource is concrete and the effect on downstream post generation is spelled out, so an agent can distinguish it from siblings like upload_brand_image or approve_post.

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?

It gives explicit when-to-use and when-not guidance: 'Call with neither assetIds nor all to see the list first,' and for the mutation path, 'only call it once the owner has actually said these are theirs, never on your own judgment.' It even names approve_post as the analogous rights step, leaving nothing to inference.

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