list_artifacts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful scoping detail that only 'finalized' artifacts are listed, but it does not disclose ordering, pagination, or failure behavior. There is no contradiction with annotations.

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 a single front-loaded sentence with no filler or redundancy. Every word contributes to the core purpose, making it very easy to scan and quickly understand the tool's role.

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 one-parameter read-only listing tool, the description is nearly sufficient, but the absence of an output schema raises the bar. It would be more complete if it clarified whether the response contains artifact content, metadata, or only URIs, and how that relates to read_artifact.

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%, and the description never mentions session_id. The parameter name is somewhat self-explanatory, and the phrase 'session artifacts' implies that session_id identifies the relevant session, but the description does not clarify the expected provenance or format of session_id beyond the schema's length constraints.

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 uses a specific verb ('List') and names a concrete resource ('finalized session artifacts and MCP resource URIs'). It is distinguishable from siblings like read_artifact and list_sessions, though the phrase 'MCP resource URIs' is jargon-heavy and leaves some ambiguity about exactly what is returned.

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?

There is no guidance about when to use this tool versus alternatives such as read_artifact, get_session, or list_sessions. The appropriate trigger condition—for example, needing artifact metadata or URIs after a run finalizes—is left entirely to inference.

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