get_selection_history

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

With no annotations, the description carries the behavioral burden. It discloses ordering (newest first) and the scope (Chrome extension selections). However, it does not explicitly state that it is read-only or non-destructive, which would be helpful for safe invocations.

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 sentences, front-loaded with the primary function. The first sentence delivers the core behavior; the second adds use-case context. No wasted words, though the description could be slightly more structured (e.g., separate purpose and params).

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 only one parameter, no output schema, and no annotations, the description covers the tool's purpose, ordering, and use-case. It is sufficient for the agent to invoke it correctly, though it could mention that results are safe to cache or that it's a read operation.

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 coverage is 100%, so baseline is 3. The description adds value by mentioning 'last N' and 'Chrome extension', providing context beyond the schema's limit field. This helps the agent understand the parameter's role in the tool's purpose.

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 it returns the last N element selections, newest first, which is a specific verb+resource. It also distinguishes from siblings like get_latest_selection (single) and other get_* tools.

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 mentions usefulness for comparing or reviewing selections, but does not explicitly state when to use this tool over alternatives (e.g., get_latest_selection) or warn against misuse. It provides context but no direct guidance.

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