get_clipboard_history

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

Discloses pure read behavior and auto-exclusion of sensitive content (passwords, OAuth tokens), compensating for absent annotations.

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?

Succinctly structured with sections for usage, behavior, and parameters; no unnecessary words.

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?

Completely covers all necessary information for a simple single-parameter tool with an output schema; describes output contents adequately.

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?

Description adds full context for parameter 'n': range 1-100, default 10, newest-first order. Input schema only provides default, so description adds significant value.

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 recent clipboard entries, specifies returned fields (timestamp, content/content-type, source app), and distinguishes from sibling tool search_clipboard.

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?

Explicitly states when to use (user references copying) and when not (text search), including the alternative tool name (search_clipboard).

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