think

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

Clearly states the tool is non-destructive and read-only: 'It will not obtain new information or change any state — it appends your thought to the log.' This is fully transparent about its behavior.

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 longer than necessary, including some meta-cognitive advice that could be seen as extraneous. While front-loaded, it could be more concise.

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 the tool's simplicity, the description covers the main aspects: purpose, usage, and behavior. It also references the sibling tool and provides procedural tips, making it fairly complete.

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 has 100% coverage, so baseline is 3. The description adds value by explaining how to use parameters like adjusting totalThoughts and using verify when nextThoughtNeeded is false.

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's purpose: 'record a structured reasoning step.' It specifies it does not obtain new information or change state, and it distinguishes itself from the sibling tool 'verify' by explaining when to use each.

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 guidance on when to use (processing results, planning, analyzing, navigating policies) and when not to use (simple single-step tasks, restating without analysis). Also instructs to use the verify tool after the final thought.

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