list_artifacts

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

With no annotations, the description must carry full behavioral disclosure. It only says 'List recent...' implying a read-only operation, but does not explain what 'artifacts' means, how 'recent' is defined, whether there is pagination, or any side effects. The lack of detail about return format or ordering is a significant gap.

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, concise sentence that is easy to parse and front-loads the action and object. However, it is extremely terse and omits critical context, but that is a content completeness issue rather than a structural flaw.

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?

Given the lack of output schema, annotations, and parameter descriptions, the tool description is insufficient for an agent to understand the full scope and usage. It does not explain what constitutes an artifact, the effect of the limit parameter, or how the output is structured. Sibling tools provide no contrast, making this description only minimally useful.

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?

The input schema has one parameter (limit) with 0% schema description coverage. The tool description does not mention the parameter or its semantics, leaving the agent to guess its purpose and valid values beyond the numeric bounds. There is no compensation for the missing schema descriptions.

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') and the resource ('recent TracePilot evidence artifacts'), giving a specific verb and object. However, it does not differentiate from sibling tools like list_targets, as 'artifacts' vs 'targets' is ambiguous without additional context.

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?

No guidance is provided on when to use this tool over alternatives. It does not mention prerequisites, appropriate scenarios, or exclude cases where other list tools (e.g., list_targets) would be more suitable.

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