Mark a question or request as resolved by linking it to the message that provides the answer, keeping thread coordination clear.
Mark a question or request resolved by a message in the same thread.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | ||
| binding_token | No | Opaque token returned by this agent's join_session or plan_session. Required for reliable identity when logical agents share an MCP connection. | |
| resolution_message_id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description conveys the primary behavioral effect—marking something as resolved—and the same-thread constraint. However, with no annotations, it carries the full burden and does not disclose side effects, permission requirements, idempotency, or validation 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?
One focused sentence with no filler. The action, target, and constraint are all front-loaded, and every word earns its place.
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, and low schema description coverage, the description remains too sparse to fully support confident invocation. It omits usage direction, side effects, and specific parameter interplay, leaving meaningful gaps for the agent.
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 description helps map message_id to the 'question/request' and resolution_message_id to the 'message in the same thread,' adding meaning beyond the titles. Binding_token already has a supportive schema description, so overall parameter meaning is adequate but not fully explicit.
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 a specific verb ('mark resolved') applied to a specific resource ('a question or request') and adds the same-thread constraint. It clearly distinguishes this from siblings like resolve_contradiction and close_thread.
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 explicit guidance on when to use this tool versus alternatives such as resolve_contradiction, close_thread, or update_task. The same-thread phrase hints at a prerequisite, but the agent is left to infer the full decision context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.