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

No annotations exist, so the description carries full burden. It mentions combining semantic relevance and recency but doesn't disclose exact algorithm, limitations, or confirm read-only nature. No destructive behavior is implied, but more transparency on behavior would help.

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: first states purpose, second gives usage guidance. Extremely concise with zero wasted words, front-loaded with key information.

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?

No output schema exists, but the description doesn't explain what the return value looks like (e.g., list of artifacts, structure). For a tool that retrieves prior context, this is a significant completeness gap. Complexity is moderate, so more detail expected.

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 baseline 3. The description does not add significant meaning beyond the schema's existing parameter descriptions. It reiterates the purpose but doesn't provide new semantic insight.

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 tool auto-pulls relevant artifacts from prior agent sessions for the current task, using semantic relevance and recency. It distinguishes itself from sibling tools that handle activities, comments, deletions, etc.

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 explicitly says 'Call this at the START of any non-trivial task to ground the agent in prior context' and notes it replaces manual copy-paste, providing clear when-to-use guidance. It lacks explicit when-not-to-use but implies trivial tasks don't need it.

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