List recent consultations

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

No annotations are provided, so the description carries the burden. It discloses ordering (newest first) and that results include status and summary, which is useful. However, it doesn't disclose whether this is a read-only operation, whether it reflects only the current session, or what happens when there are no consultations. The 'from this session' scoping is a meaningful behavioral detail.

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, front-loaded sentence that conveys the resource, scope, ordering, and included fields with zero waste. 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?

For a simple list tool with one optional parameter and no output schema, the description is nearly complete. It could mention that the output is a list of consultations with status and summary, but that's already implied. The main gap is not explaining the 'limit' parameter, though the schema covers it.

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 0%, so the description must compensate. It doesn't explain the 'limit' parameter at all, but the schema itself defines it as an integer with min/max, which is self-explanatory. The description adds no meaning beyond the schema for the parameter, but the parameter is simple enough that this is a minor gap.

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 ('List'), a clear resource ('recent consultations from this session'), and adds ordering ('newest first') plus included fields ('status and one-line summary'). This clearly distinguishes it from siblings like consult_get (single consultation retrieval) and consult_start (initiating a consultation).

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?

The description implies this is for browsing recent session consultations, which is distinct from consult_get (retrieving a specific one) and consult_cancel (cancelling). It doesn't explicitly state when not to use it or name alternatives, but the context is clear enough for an agent to select it appropriately.

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