tor_list_sessions

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

The annotations already declare readOnly, idempotent, and non-destructive behavior, but the description adds a critical behavioral guarantee: it never returns cookie values. This is beyond the annotations and helps the agent understand the tool won't expose sensitive data, which is valuable context for a session-management tool.

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 a single, compact sentence with no filler words. It front-loads the core action and adds a necessary clarification, making it perfectly sized for its purpose.

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 parameters and a clear list operation, the description is entirely sufficient. The output schema is already present, so it doesn't need to explain return values, and the safety annotations cover behavioral expectations. The only addition, 'never cookie values,' strengthens completeness.

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?

With zero parameters, the schema fully describes the invocation contract (empty object), and the rule for 0 parameters sets a baseline of 4. The description doesn't elaborate on parameters, but none exist, so this is 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?

The description uses a specific verb 'List' and a distinct resource 'saved session metadata,' clarifying that it enumerates sessions rather than loading, saving, or deleting them. The parenthetical 'never cookie values' further distinguishes its scope, making the purpose unambiguous even among many sibling tools.

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 that this tool is used to view existing saved sessions, but it does not explicitly state when to choose it over alternatives like tor_load_session or tor_delete_session. There is no scenario guidance or exclusionary language, so it only partially helps the agent decide when to invoke it.

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