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

readOnlyHint=true already declares the safety profile, and the description adds real context beyond it: newest-first ordering, a hard cap of 50, which fields come back, and that image_url appears only for images and PDFs. Missing is any statement about pagination past 50 or what happens when nothing exists.

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 scope and return contents are front-loaded in the first sentence, followed by the filter note and the call condition. Dense but nearly every clause carries information; "A document or email has no picture" is slightly awkward phrasing for a useful clarification.

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 job of describing the return payload (field list, image_url exception) plus ordering, limit, filter and invocation trigger. Nothing essential for a correct call is left out.

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%, so the description must carry the parameter burden. It only says "kind narrows it to one kind," which essentially restates the name, and never maps the enum values (og_image, pdf, substack_post, markdown) onto the categories it listed earlier.

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 (list the generated artifacts in the user's active space) and enumerates the item types covered: images, emails, PDFs and documents. It also names the returned fields (artifact_id, kind, title, status, brand, image_url), so the agent knows exactly what this tool yields.

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?

"Call it when the user asks what they have generated or refers to an earlier one" gives clear triggering context, and "kind narrows it to one kind" signals the filtering behavior. It stops short of naming the alternative for a specific item (get_artifact/read_artifact exist as siblings) or stating exclusions.

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