list_articles

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

With no annotations, the description carries the full transparency burden. It discloses the read-only nature (list) and specifies return fields (title, slug, summary, domain). It does not mention potential pagination, sorting, or permissions, but these are not critical for a simple, safe listing operation.

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, well-structured sentence that leads with the action, then the optional filter, then the return value. Every word contributes and there is no fluff or repetition.

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 tool's simple nature (one optional param, no output schema), the description is complete: it explains the main action, the filter option, and the return fields. No crucial missing context is evident.

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 schema already fully covers the only parameter 'domain' with an enum and description. The description adds minimal extra meaning beyond restating 'compliance domain' and the optional filtering behavior, so the baseline 3 applies.

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' with a clear resource 'wiki articles', and indicates optional filtering by domain. It distinguishes itself from siblings like search_wiki (searching) and get_article (retrieving a single article) by explicitly listing all articles.

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 clear context: use to list all articles, optionally filtered by compliance domain. It doesn't explicitly contrast with alternatives or state when not to use, but the 'list all' scope clearly differentiates it from search/retrieval siblings.

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