unclick_workspace_read

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: UTF-8 text only (no binary), no personal OAuth connection is touched, and paths are hard-limited to Context or System Information (a path-traversal guard). It omits failure behavior for missing files, but the added constraints are substantive.

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, zero padding, with the access restriction front-loaded before the scope and path limits. Every clause carries information an agent needs before invoking.

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 read-only tool with full annotation coverage and no output schema, the definition covers who may call it, what it reads, encoding, and where it can read from. Only minor gaps remain, such as missing-file errors and size limits.

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 description coverage is 100%, and both parameters carry their own descriptions including the enum mapping to concrete directories. The description only reinforces the hard path restriction already implied by the enum, so the schema is doing the heavy lifting — baseline 3 is appropriate.

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?

States a specific verb and resource (read a UTF-8 text file) plus the exact storage scope (shared UnClick Dropbox workspace, not a personal Dropbox connection). This implicitly separates it from dropbox_read_file and the sibling unclick_workspace_list/write, though it never names those siblings explicitly.

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 gives a strong gate — 'Superuser/God only' — and enumerates the two permitted areas, which tells an agent who may call it and on what. It does not say when to prefer this over unclick_workspace_list or unclick_workspace_write, so routing is only implied.

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