get_chat_history

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

The description adds context that the data is local and stored in SQLite, complementing the readOnlyHint annotation. However, it does not clarify the ordering of messages or the effect of the limit parameter on the retrieval behavior.

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?

A single sentence of 13 words conveys the essential purpose without extraneous detail, making it highly efficient and readable.

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?

While the output schema likely covers return values, the lack of parameter documentation and usage guidance leaves the agent underinformed for a tool with optional parameters and no sibling differentiation.

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 has 0% description coverage, and the description does not explain either parameter ('limit' or 'session'). The agent must infer their meaning from names alone, which is insufficient.

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 returns the most recent messages for a local chat session from SQLite, using a specific verb and resource that distinguishes it from sibling tools like 'clear_chat_history' or 'chat'.

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?

No guidance is provided on when to use this tool versus alternatives like 'stateful_chat' or 'search_knowledge'. The description does not mention prerequisites or scenarios where the tool is inappropriate.

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