list_artifacts

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

With no annotations provided, the description carries the full burden. It states the operation is a listing operation and clarifies the local scope and filtering capability. However, it does not disclose pagination behavior, output shape, or the fact that 'all' artifacts are likely returned in pages based on the limit/items_per_page parameters.

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, making it easy to scan. It sacrifices some useful context (pagination, usage guidance) for brevity, but the wording itself is efficient.

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?

The description is adequate for a basic list-and-filter operation, especially because all parameters are described in the schema. Yet it has clear gaps: no output schema, no mention of pagination semantics, and no guidance on how this tool relates to the many sibling tools.

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 100%, so the parameters themselves are already fully documented. The description adds only the generic notion of 'optional filtering', which does not meaningfully clarify the ambiguous relationship between 'limit' and 'items_per_page'.

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 identifies the exact resource ('Maven artifacts in the local repository') with a clear qualifier ('optional filtering'). This distinguishes it from sibling tools focused on remote search, analysis, extraction, and dependency resolution.

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 phrase 'in the local repository' provides clear context that this tool is for local artifact enumeration, in contrast to tools like search_maven_central or get_remote_versions. However, it does not explicitly mention when to prefer alternatives or describe exclusions.

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