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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description focuses on what it adds: metadata-only output, no text content, and the instruction to stay silent on empty results. It stops short of saying whether results are ordered or bounded, which is the only remaining behavioral gap.

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?

Six short sentences, front-loaded with purpose then scope then usage rules, with no repetition of structured data. The empty-result sentence is unusual but earns its place by preventing spurious user-facing output.

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?

With no output schema, the description compensates by listing the returned metadata fields, and it fully covers invocation conditions for a one-optional-parameter read tool. Minor incompleteness around result ordering/volume is the only thing an agent might still wonder about.

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% and the single workspace_id parameter is fully documented in the schema, including the list_workspaces reference. The description's 'optionally for one workspace' restates the schema without adding syntax or semantics, so the baseline 3 applies.

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 ('List the user's uploaded documents') and immediately enumerates the metadata fields returned (id, file name, type, size, processing status, workspace, dates). It also distinguishes itself from adjacent operations by declaring it does not return document text and does not upload 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?

Gives an explicit trigger ('when the user asks which files ISMS Copilot holds'), an explicit exclusion ('do not call it before a question unless the task needs the user's own documents'), and even handling guidance for empty results. Nothing is left to inference.

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