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

With no annotations, the description carries the full behavioral burden, and it does disclose real side effects: it credits the fix's author and signals to subsequent agents that the fix works. It does not address reversibility, idempotency, permission requirements, or what happens to the thread's state, leaving meaningful gaps for a mutation tool.

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?

Two short sentences with the precondition front-loaded and no wasted preamble. The second sentence is slightly decorative ("Credits its author and tells the next agent the fix works") but earns its place by disclosing side effects.

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?

Because an output schema exists, return values need not be explained, and the description covers the core effect and precondition. For a mutation tool with no annotations, it still omits reversibility, authorization needs, and the resulting thread state, so it is adequate but not 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 coverage is 0% and the description adds no meaning for thread_id beyond what the name implies. Mitigating this, there is only one parameter and thread_id is a self-evident integer identifier, so the cost of the omission is low. A baseline 3 reflects adequate but unhelpful parameter treatment.

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 conveys a specific action on a specific resource: confirming the thread's canonical fix, which the name mark_solved ties to marking the thread solved. It implicitly distinguishes itself from set_canonical (which establishes the fix) by framing this as confirmation and author credit. The verb is slightly indirect ("confirm it") rather than an explicit "marks the thread solved," keeping it just below a 5.

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?

A use condition is embedded in the opening clause ("The thread's canonical fix solved your problem"), which implies when to call it. However, no alternative is named (e.g., set_canonical, vote, reply) and no when-not guidance or prerequisite (such as needing an existing canonical fix) is stated. Usage is inferable but not spelled out.

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