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

No annotations exist, so the description carries the load: it discloses read-only listing semantics, cross-harness aggregation, and newest-first ordering, which the schema does not. It doesn't say whether results are paginated or what a session entry contains, but for a simple listing that gap is modest.

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 scope and ordering front-loaded before the usage cue. No filler and nothing repeated from the schema.

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 zero-required-parameter read tool with a fully documented schema and no output schema, the description gives enough to call it correctly and order results. Only the shape of returned sessions and any pagination behavior remain unstated.

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%, documenting limit, project default and the platform harness values, so baseline is 3. The description adds only that filtering is by project scope and that results are newest first, no extra syntax or format detail.

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?

Specific verb (List) plus resource (agent sessions) with explicit scope (this project), breadth (across six named harnesses) and ordering (newest first). An agent can tell this apart from drive_resume or drive_recall without inspecting schemas.

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 to find prior work to continue" gives a clear situational cue that implicitly routes the follow-up action to drive_resume. It stops short of naming an explicit alternative or a when-not condition.

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