ingest

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

Given no annotations, the description discloses behavior: it ingests new transcripts, is automatic, and can be triggered manually. No further behavioral details needed for a simple 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?

Two sentences: first defines purpose, second explains usage patterns. No extraneous words, front-loaded, efficient.

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?

Covers purpose and usage adequately for a simple tool with one parameter and an output schema (unknown content). Lacks explanation of the parameter's role, but overall complete enough.

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 has a single parameter 'max_msgs' with default 5000 and no description. The tool description does not mention or explain this parameter, so the agent gets minimal guidance despite low schema 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 clearly states it ingests new Claude Code transcripts, with a specific verb ('ingest') and resource ('transcripts'). It also distinguishes its usage pattern (auto-runs on session start, manual for backfill/long absence) 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?

Provides explicit context: auto-runs on session start and should be called manually for backfill or after long absence. This tells the agent when to use it, though it doesn't explicitly list alternatives or when not to use it.

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