remember

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the transcript is fetched, chunked with timestamps, and indexed for search, and that the tool returns the stored item's id. This is meaningful process transparency, though it omits potential edge cases like duplicate URLs or unsupported media types.

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?

The description is three sentences long, front-loads the core purpose, and each sentence adds distinct value: input types, processing behavior, and output usage. No filler or repetition of schema info.

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 tool with two parameters and an output schema, the description covers input, processing pipeline, and return value, and connects to related tools. It lacks explicit constraints like authentication or format limitations, but given the output schema, this is sufficiently complete for an agent to use the tool correctly.

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 0%, so the description fully compensates. It explains that `url` accepts a YouTube URL or podcast RSS feed URL, and that `episode` is an optional title filter defaulting to the latest episode. Both parameters are semantically enriched beyond the bare schema.

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 opens with a specific action and target: 'Add a YouTube video or podcast episode to the second brain.' It clearly distinguishes this from sibling tools (recall, library, transcript, digest, forget) by focusing on ingestion, not retrieval or deletion.

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?

It explains how to use the tool: pass a YouTube URL or podcast RSS feed, optionally with an episode filter defaulting to the latest episode. It also says the returned id should be used with `transcript` and `forget`, giving follow-up context. It does not explicitly state when not to use it, but the usage context is clear.

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