context_list

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

With no annotations provided, the description is the sole source of behavioral disclosure. It states the action but does not disclose whether the operation is read-only, what the return payload looks like, whether pagination applies, or any permission requirements. The word 'list' implies a read operation, but this is not made explicit.

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 concise sentence with the verb front-loaded. Every word earns its place; zero wasted words. It is appropriately sized for the tool's simplicity.

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?

The tool is simple with one parameter, no output schema, and no annotations, but the description gives no indication of the response format, whether 'all' includes metadata, or if there are pagination limits. While the action is clear, the lack of any return-value context leaves a gap in completeness for an AI agent to understand what to expect.

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 schema description coverage is 100% since 'session_id' has the description 'Session identifier'. The tool description adds no additional semantic detail beyond the schema, so it meets the baseline but does not exceed it. No examples, format hints, or relationship to other parameters are provided.

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 the specific verb 'List' with the resource 'context values' and scopes it to 'for a session', clearly distinguishing it from sibling tools like context_get (single value) and context_set (write operation). It is immediately obvious what the tool does.

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 usage ('List all context values for a session') but gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as context_get for a single value or context_search for filtering, so the guidance is only implied by contrast with sibling tool names.

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