Scan recent agent-mode sessions to detect context notes indicating completed tasks; set the days parameter to define the lookback window.
Scan recent agent-modes sessions for context notes that may indicate task completion.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Number of days back to scan |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It does not state whether the scan is read-only, whether it has side effects, what authentication or rate limits apply, or what the returned data looks like.
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?
A single sentence that is front-loaded with the verb and resource. It is concise and has no wasted phrases, though the wording 'may indicate' is slightly vague.
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 one-parameter scan with no output schema, the description is minimally adequate. It omits what a 'context note' is and does not clarify the relationship to task completion, leaving an agent with only a broad purpose.
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 description coverage is 100%, so the 'days' parameter is already documented with its default, minimum, and maximum. The description adds no extra semantic detail about the parameter, making the baseline score appropriate.
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?
States a specific verb (scan), resource (recent agent-modes sessions), and target (context notes that may indicate task completion). It is clear what the tool does but does not distinguish it from the sibling analyze_session_for_tasks.
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?
No explicit guidance on when to use this tool versus alternatives such as analyze_session_for_tasks. The phrase 'may indicate task completion' hints at a use case but does not specify conditions or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.