list_recent

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

No annotations are provided, so the description carries the full disclosure burden. It states the ordering but leaves the notion of 'newest' ambiguous—is it creation time or last-update time? It also does not disclose what each returned page entry contains (title, excerpt, just ID?) or how pages updated multiple times within the window are deduplicated. These behavioral gaps are meaningful for an ordering-based time range tool.

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?

Single sentence, zero filler. It front-loads the verb and resource, then adds temporal filtering and ordering. Every word earns its place.

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 simple list tool with full schema coverage, this is mostly adequate; however, with no output schema and no annotations, the description should clarify the return shape and the ordering key. Without that, an agent invoking the tool cannot fully anticipate whether subsequent calls are needed (e.g., read_wiki_page for content).

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 already documents both parameters fully (days with default 7, limit with default 20 and max 100), so the baseline is 3. The description does not add parameter-level semantics beyond the schema, which is acceptable at 100% coverage.

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'), a concrete resource ('wiki pages'), and precise temporal scope ('added or updated within the past N days') with ordering ('newest first'). This clearly distinguishes it from sibling tools like search_wiki, read_wiki_page, and find_related without needing to open the schema.

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 description establishes clear contextual usage: any time you want recently added/updated wiki pages rather than search or semantic retrieval. It does not explicitly name when-not-to-use alternatives, but the temporal filter and ordering make the intended scenario obvious among the sibling tools.

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