process_thought

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

No annotations are provided, so the description carries the full burden. It implies a stateful write ("record") but says nothing about whether a session must be initialized, whether thought numbers must be sequential, whether prior thoughts are overwritten or appended, or whether this state persists across calls.

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?

A single well-formed sentence with no waste and the core action front-loaded. But for an 8-parameter stateful tool, the brevity reads as under-specification rather than disciplined conciseness.

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?

With no annotations, no output schema, four required parameters, and 0% schema description coverage, the one-sentence description leaves an agent unable to determine sequencing rules, required context, or what a call returns.

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% across 8 parameters, so the schema offers no help. The description only gestures at one of them ("stage tracking"); it adds no meaning for thought, thoughtNumber, totalThoughts, nextThoughtNeeded, tags, axiomsUsed, or assumptionsChallenged, leaving most of the tool's semantics unexplained.

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?

"Record a structured thought step in a reasoning process with stage tracking" gives a verb and a resource, so it exceeds a pure restatement of the name. However, "reasoning process" and "thought step" are vague and the description does nothing to separate this from the task-oriented siblings (reflect_task, plan_task, analyze_task), which also manipulate reasoning artifacts.

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?

There is no statement of when to use this tool, when not to, or which sibling it replaces. Given twelve task-related siblings, the absence of any routing guidance is a real gap rather than a minor omission.

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