auto

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

No annotations are provided, so the description bears full responsibility. It mentions 'POST fallback (0-token)' and actions like extract, topic-shift, auto-link, and save, but does not detail side effects, prerequisites, or limitations. The description gives a basic sense of behavior but lacks depth.

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 extremely concise: one sentence stating the action, followed by a clear usage guideline. No extraneous words. Information is front-loaded and every sentence is purposeful.

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?

The tool has 2 parameters and no output schema or annotations. The description covers the core action and usage context, but does not mention return values, error conditions, or detailed behavior. It is minimally adequate but leaves gaps for a complete understanding.

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 is 3. The tool description does not add significant meaning beyond what the schema already provides for the parameters. The schema descriptions for text and context are adequate, and the tool's overall description adds minimal parameter-specific context.

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 performs a one-shot extract, topic-shift, auto-link, and save. It explicitly contrasts with store_turn, saying 'Prefer a curated store_turn when you can pick the concepts yourself; use auto only for throwaway turns.' This provides a specific verb+resource combination and distinguishes it from a sibling.

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 provides explicit guidance on when to use this tool versus store_turn: 'Prefer a curated store_turn when you can pick the concepts yourself; use auto only for throwaway turns.' This clearly indicates usage context and alternatives.

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