qllm_claude_code_sessions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable context: 'Raw secrets are not read from settings,' which goes beyond the annotations and clarifies security behavior. No contradictions.

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 sentences plus an Args/Returns block. It is front-loaded with the purpose and efficient, with no extraneous information. The Args/Returns block is slightly redundant given the schema but does not detract.

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?

Given the tool has one parameter with clear sub-properties, annotations, and an output schema, the description covers the essential use case and mentions security ('Raw secrets are not read from settings'). It does not explain session structure, but that is reasonable domain context.

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 description lists parameters briefly: 'Cwd, limit, prompt inclusion, and output format.' However, the input schema already provides detailed descriptions for each sub-property (e.g., cwd's description, limit's min/max). The description adds little meaningful context beyond the schema.

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 tool inspects recent local Claude Code JSONL sessions for models and prompts. This is a specific verb+resource that distinguishes it from siblings like qllm_claude_code_run (execution) and qllm_list_models (listing).

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 when to use (to inspect sessions) but does not explicitly contrast with siblings or provide when-not or alternative tool references. The sibling list is provided externally but not leveraged in the description.

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