think

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

Discloses persistence to SQLite, auto-creation of session on first call, and appending to active branch. Without annotations, this provides sufficient behavioral context, though could mention limits.

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?

Four concise sentences with no wasted words. Front-loaded with core purpose, then persistence, then usage, then exclusion. Highly 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?

Given simple single-parameter tool with no output schema, the description covers purpose, behavior, persistence, session management, and usage boundaries. Complete for effective usage.

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 already covers the parameter with 100% coverage. Description adds context about 'current thinking step' but doesn't add significantly new semantics beyond what schema provides.

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?

Clearly states 'Add a numbered thought to your reasoning chain' with specific verb and resource. Distinguishes from sibling tools like branch and complete by focusing on adding thinking steps.

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?

Explicitly says 'Use for any multi-step reasoning' and 'Do not use for simple, single-step answers', providing clear when-to-use and when-not-to-use guidance.

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