think_about_task_adherence

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

Annotations indicate readOnlyHint=true, and the description doesn't contradict this, as 'Call before code edits' implies a preparatory step rather than a mutation. The description adds minimal behavioral context beyond the annotations, such as the timing aspect, but doesn't disclose other traits like what the tool evaluates, its output format, or any side effects. With annotations covering safety, a baseline 3 is appropriate.

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 with a single sentence ('Call before code edits'), which is front-loaded and wastes no words. Every part of the description serves a purpose in providing usage timing, making it efficient and well-structured.

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 has 0 parameters, annotations provide readOnlyHint, and an output schema exists, the description is minimally adequate. However, it lacks details on what the tool does (e.g., evaluates adherence to what task), its output, or how it integrates with the workflow. For a tool with a suggestive name and siblings like other 'think_about' tools, more context would improve completeness.

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 0 parameters, and the input schema has 100% description coverage, so there are no parameters to document. The description doesn't need to add parameter semantics, and it doesn't introduce any confusion. A baseline score of 4 is given for tools with no parameters, as there's nothing to compensate for.

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 'Call before code edits' states a timing directive but doesn't specify what the tool actually does. It mentions a procedural step rather than the tool's function, making the purpose vague. The tool name 'think_about_task_adherence' suggests it involves reflection or evaluation, but this isn't clarified in the description.

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 clear context for when to use the tool ('before code edits'), which helps the agent time its invocation appropriately. However, it doesn't specify alternatives or exclusions, such as whether it should be used before all edits or only specific types, or how it differs from sibling tools like 'think_about_collected_information' or 'think_about_whether_you_are_done'.

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