document_list

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

Annotations already declare readOnlyHint and a non-destructive hint, and the description's 'List' verb agrees with them. It adds the scoping detail that only saved documents in the workspace are returned, but does not disclose output shape, ordering, or pagination behavior.

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?

One short sentence contains the operation, resource, and scope with no filler. It is front-loaded and every word earns its place.

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 zero-parameter, read-only list operation, the description is largely complete: it states what is listed and the workspace scope. The only missing context is the exact returned document fields, which may be learned from the tool response.

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 no parameters, and schema description coverage is effectively 100%, so there is nothing for the description to clarify. The 0-parameter baseline applies, and the description introduces no conflicting parameter information.

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 uses a concrete verb ('List') and a specific resource ('saved documents in this workspace'), making the tool's purpose unambiguous. It is naturally distinct from siblings like document_read or document_create because it names an enumeration operation over saved documents.

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 the tool should be used when an agent needs an inventory of saved documents in the current workspace. It does not explicitly name alternatives or exclusions, but the workspace qualifier and list semantics provide usable context for a zero-argument tool.

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