Serena

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

Annotations indicate readOnlyHint=true and destructiveHint=false, which the description does not contradict. The description adds behavioral context by emphasizing the tool's importance in specific scenarios (long conversations, back-and-forth) and its mandatory use before certain code operations. However, it does not disclose additional traits like rate limits, auth needs, or detailed behavioral outcomes beyond what annotations provide, resulting in moderate value addition.

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 appropriately sized with three sentences that are front-loaded: the first states the purpose, the second adds context, and the third provides usage guidelines. Each sentence adds value without redundancy, though it could be slightly more structured for optimal clarity.

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 complexity (low, with 0 parameters), rich annotations (readOnlyHint, destructiveHint), and presence of an output schema, the description is mostly complete. It covers purpose, usage guidelines, and context, but lacks details on output behavior or specific outcomes. However, with annotations and output schema handling safety and returns, the description is sufficient for the tool's role.

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 input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description does not discuss parameters, which is appropriate. Baseline score is 4 for zero parameters, as the description does not need to compensate for any schema gaps.

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 states the tool is for 'thinking about the task at hand and whether you are still on track,' which provides a vague purpose. It mentions a specific context ('conversation has been going on for a while'), but does not clearly distinguish it from sibling tools like 'think_about_collected_information' or 'think_about_whether_you_are_done.' The purpose is understandable but lacks specificity in differentiating its role.

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 explicitly states when to use this tool: 'Especially important if the conversation has been going on for a while and there has been a lot of back and forth' and 'This tool should ALWAYS be called before you insert, replace, or delete code.' It provides clear context and exclusions, naming specific sibling tools (insert, replace, delete code) as alternatives or prerequisites, making usage guidelines highly explicit.

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