list_artifact_examples

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

With no annotations, description adds behavioral context: slug matching parent node, path structure example. But lacks disclosure of side effects, idempotency, or access requirements.

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 concise sentences front-loading purpose, adding necessary detail on slug matching, and providing usage guidance. No wasted words.

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?

Output schema exists, so no need to detail returns. Description covers what the list contains and how to use with other tools. Minor gap on ordering/filtering but adequate for zero-parameter 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?

No parameters in input schema. Baseline 4 applies. Description adds value by explaining output structure (slug matching) and usage context beyond 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?

Clearly states verb 'List', resource 'filled-in artifact examples', and context 'anchored to the shared engagement context'. Distinguishes from sibling get_artifact_example by listing vs fetching specific.

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?

Provides explicit usage sequence: first get context via get_engagement_context(), then list, then optionally fetch specific via get_artifact_example. Clear when to use it, though does not state when not to.

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