ingest

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

Annotations are neutral (no hints about read-only, idempotency, or destructiveness). The description adds the behavioral fact of auto-running, but does not explain side effects, required permissions, or what the ingestion process entails beyond 'ingest transcripts'. More nuance would improve transparency.

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 concise sentences that front-load the purpose and immediately provide usage context. No wasted words.

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?

While the tool has an output schema (not shown) and minimal parameters, the description lacks details on what happens during ingestion (e.g., state changes, error conditions). It is sufficient for a simple tool but incomplete for understanding all implications.

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?

There is one parameter (max_msgs) with a default but no description in the schema (0% coverage). The tool description does not mention the parameter at all, leaving the agent to guess its purpose and effect. This is a critical gap.

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 specifies the verb ('Ingest'), the resource ('new Claude Code transcripts'), and distinguishes when to use it (auto-runs on session start, manual for backfill or after absence). This sets it apart from sibling tools.

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 gives explicit guidance on when to call the tool manually (backfill, long absence) and notes it auto-runs. While it doesn't explicitly state when not to use it or list alternatives, the context is clear enough.

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