list_artifacts

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

With no annotations provided, the description carries the transparency burden. It discloses the output format ('Returns the markdown files with their sizes and metadata summaries'), which is helpful, but it does not mention pagination, limits, or behavior when the conversation has no artifacts. Overall, it provides meaningful context beyond the name.

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 description is two concise sentences, front-loaded with the primary action, and contains no unnecessary repetition or filler. Every word adds value.

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 simple tool with one parameter and no output schema, the description adequately covers the main behavior: listing artifacts with basic metadata. It does not mention error cases or ordering, but these are not critical for the tool's basic use. It is reasonably complete given the tool's simplicity.

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% and the parameter definition already states 'UUID of the conversation'. The description adds that the conversation is the scope for listing artifacts, but this is a minor clarification consistent with the parameter's purpose. It does not significantly enhance semantics beyond 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 action ('List all artifact files') and the scope ('in a specific conversation'), and it distinguishes the tool from siblings like list_conversations and read_artifact by focusing specifically on artifact enumeration within a conversation.

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 implies the tool is used to list artifacts in a conversation but does not explicitly mention when to use it over alternatives like search_artifacts or read_artifact. There are no exclusions or alternative direction provided, so usage is implicit rather than explicit.

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