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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's contribution is the scoping ('in this space', i.e. the space currently selected via use_space) and the fact that content is kept 'word for word'. With no output schema, naming the returned fields is meaningful behavioral disclosure; it stops short of noting ordering, pagination, or empty-result behavior.

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?

Two sentences, both load-bearing: the first defines the result set and its shape, the second gives the next action. The purpose is front-loaded with no preamble or restatement of the title.

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 zero-parameter read-only listing with no output schema, the description covers scope, returned fields, and the follow-up tool, which is what an agent needs to act. Minor residual gaps are ordering/limits and explicitly stating that the space comes from the active space context.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies the listing is implicitly scoped to the current space rather than requiring a space argument.

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?

States a specific verb and resource ('list ... artifacts') plus the exact scope ('what earlier chats and sessions in this space produced and kept'). It also enumerates what each entry contains (id, title, one line, version count), so it is distinguishable from siblings like evidence or recall at a glance.

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?

Explicitly routes the agent to the sibling open_artifact before revising or building on anything listed, which is the key follow-up action. It does not, however, contrast with the other plausible retrieval siblings (recall, evidence, expand), so selection among those is left to inference.

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