get_clipboard_files

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

No annotations are provided, so the description carries the full burden. It states it returns file paths or an error, but does not explicitly disclose that the operation is read-only (non-destructive) or mention any privacy/security concerns. It is adequate but minimal.

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?

The description is extremely concise: two sentences, one for purpose and one for return format. Every sentence adds value with no waste.

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?

For a tool with no parameters and an output schema (though not provided), the description is complete. It explains what the tool returns (file URLs or error message), covering all necessary context for a simple 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?

There are zero parameters and schema coverage is 100% (trivially). The description does not need to add param info. Baseline for zero parameters is 4, and the description is correct and sufficient.

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 file URLs from the macOS clipboard. It uses a specific verb ('Return') and resource ('file URLs on macOS clipboard'), which distinguishes it from siblings like get_clipboard_text (returns text) and set_clipboard_files (sets files).

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 implies when to use (when file URLs are needed from clipboard), but does not explicitly state when not to use or mention alternatives. No guidance on distinguishing from get_clipboard_text or set_clipboard_files, though the name and description hint at the distinction.

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