dsh_history

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

No annotations are provided, so the description carries the behavioral burden. It explicitly discloses that the read is bounded, that hasMore is retained, and that no session is cancelled, which are meaningful operational traits. It does not detail every possible side effect or response format, but the key behavioral guarantees for this kind of read tool are present.

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?

Two short sentences with no filler. The primary action is front-loaded, and the negative guarantee about session cancellation earns its place. This is appropriately concise.

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 description covers the essential behavior but lacks usage routing, explicit parameter semantics, and return-format detail, and there is no output schema to fill that gap. For a two-parameter tool with a pagination flag, this is adequate but not fully complete.

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 needed to compensate by explaining sessionId and maxMessages; it does not mention either parameter by name. Only the word 'bounded' hints at the role of maxMessages, while sessionId is left to be inferred from the schema and tool name.

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 ('Read') and a specific resource ('initial history snapshot'), and it adds useful scope by saying the snapshot is bounded and that hasMore is retained. It is clear about the core action, though it does not explicitly contrast with sibling tools such as dsh_sessions or dsh_prompt.

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?

There is no guidance about when to use this tool versus alternatives like dsh_sessions or dsh_prompt. The word 'initial' implies a first snapshot, but no explicit when-to-use, when-not-to-use, or alternative routing is provided.

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