cursor_history_show

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

No annotations; description implies read-only but doesn't confirm. Includes content scope (messages, tool calls, responses) but omits auth requirements, data source, or side effects.

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?

Single sentence with no redundancy, front-loaded with action and target.

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?

Simple tool; schema covers only param. Description explains output includes messages/tool calls/responses. Lacks return structure or format, but adequate for typical show tool.

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 already describes sessionIndex with meaning (1-based, from list). Description adds no extra parameter info beyond schema, achieving baseline.

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?

Description clearly states the tool retrieves full session content, distinguishing it from siblings like list (indexed listing) and search (querying). Verb 'show' matches resource 'history'.

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 on when to use vs. siblings. Doesn't mention prerequisite of list to obtain sessionIndex or alternatives like search.

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