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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds value by showing that prefix filters by folder, but it does not disclose limit behavior, pagination, ordering, or whether listing is recursive. Given the annotation coverage, this is adequate but not rich.

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 two short sentences with no filler. The core purpose comes first, and the prefix example earns its place by clarifying a non-obvious usage pattern.

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 simple read-only file listing tool, this is mostly sufficient: the agent knows to pass workspace_id and can use prefix for folders. However, there is no output schema and no mention of what the response contains or how limit/pagination behaves, leaving some uncertainty.

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 0%, so the description must carry the parameter-documentation burden. It only explains the prefix parameter; workspace_id, limit, and api_token receive no additional meaning beyond their bare names and defaults.

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 states a clear action and resource: 'List files in a workspace.' This differentiates the tool from siblings like list_workspaces (lists workspaces) and read_file (reads file contents). The prefix example adds further precision about scope.

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 prefix guidance — 'Use prefix like drafts/ to list a folder' — gives concrete, actionable usage context. It clearly implies workspace-scoped file listing, though it does not explicitly contrast with alternatives or state when not to use this tool.

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