pscribe_sessions

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

With no annotations, the description carries the full burden. The word 'List' clearly signals a read-only operation, and the return fields are disclosed. However, it does not explicitly state that this is non-destructive, nor does it clarify sorting behavior or any side effects, which would be useful but are not critical for a listing operation.

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?

The description is two concise sentences, front-loading the core purpose and then listing return fields. Every word earns its place, with no redundancy or filler.

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 adequately complete: it states the action, the resource, and the return payload. It does not explain what 'recent' means or how the limit interacts with results, but these are minor gaps given the tool's simplicity.

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 input schema fully covers the only parameter (limit) with a description, so the schema does the heavy lifting. The description does not add any additional semantic detail about the parameter beyond what is already in the schema, hence the baseline score of 3.

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 clearly states the verb 'List' and the resource 'recent transcription sessions', which distinguishes it from sibling tools that start, stop, or inspect sessions. It also specifies the exact returned fields (session ID, date, duration, segment count), leaving no ambiguity about the tool's function.

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 tool is for viewing session history, but it does not explicitly contrast it with alternatives like pscribe_status (current session) or pscribe_tail (session content). There is no 'when to use this vs. other tools' guidance, though the simple verb+resource makes the primary use case clear.

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