think_about_task_adherence

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

No annotations are provided, so the description must carry the transparency burden. It indicates this is a cognitive check, but it does not explicitly state whether it has side effects, what happens when called, or why the "always before code" rule matters. It is not misleading, but it under-specifies 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 only three sentences, front-loads the primary purpose, and then adds a clear usage condition and a specific rule. Every sentence contributes necessary information with no waste.

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 simple parameterless tool with an output schema, the description covers purpose, timing, and a firm usage rule. It does not mention alternatives or explicitly say it is side-effect free, but the tool's simplicity and the presence of an output schema lower the burden.

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?

The tool has zero parameters and schema description coverage is vacuously 100%, so there is nothing for the description to add about parameters. The baseline of 4 for parameterless tools applies.

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 function with a specific verb and resource: "Think about the task at hand and whether you are still on track." It distinguishes itself from sibling thinking tools by tying the usage to a concrete action: "always be called before you insert, replace, or delete code."

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 strong contextual usage guidance: "Especially important if the conversation has been going on for a while" and a firm rule: "should ALWAYS be called before you insert, replace, or delete code." It does not explicitly mention alternatives or when not to use it, but the context is clear.

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