n2_work_sessions

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

With no annotations, the description carries the full behavioral burden and does not state that this is a read-only listing, whether it is scoped to a project or user, or what 'pending Mimir collection' means operationally. It hints at a resume workflow but never explains the state transition or what a caller must do with the returned sessionId.

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?

It is a single front-loaded sentence with no filler, which is good. However, the trailing clause about the sessionId is confusing rather than informative, so the brevity comes at the cost of accuracy rather than being efficiently dense.

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 tool with no annotations, no output schema, and a completely undocumented parameter, the description does far too little. It also leaves 'pending Mimir collection' undefined, a domain concept an agent would need in order to interpret results.

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 single parameter 'project' is never explained by the description. Worse, the description instructs the caller to 'use the exact sessionId', a value that does not exist in the input schema, which misdirects rather than clarifies.

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 verb 'List' plus 'unfinished work and completed work' gives a rough sense of the resource, and the mention of resuming hints at what comes next. But the resource is never named as a session list, and the phrase 'with pending Mimir collection' is opaque, so an agent cannot cleanly separate this from n2_mimir_study_sessions or n2_work_log.

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?

'Use the exact sessionId to resume' implies a resume workflow, but no sibling is named and no condition distinguishes this from n2_work_start, n2_work_claim, n2_work_log, or n2_mimir_study_sessions. There is no guidance on when not to use it, nor on prerequisites for resuming.

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