Workspace Roots

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

Annotations already declare readOnlyHint=trueabb, so the description adds value by explaining the scoping relationship among tools and how allowed directories are configured. It does not describe return format, but the zero-parameter nature makes the behavior straightforward.

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?

Three sentences with no filler. The core purpose is front-loaded, followed by usage guidance and configuration sources, all concisely.

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 discovery tool, the description fully covers what the agent needs: what the tool lists, why to call it first, how access is configured, and that all sibling file tools are scoped to these roots.

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, so the schema needs no additional explanation. The description adds useful context about how directory access is configured, more than the schema alone would provide.

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 action ('List') and resource ('allowed workspace root directories'), and immediately establishes its unique role as the entry point for path discovery. The distinction from the sibling 'list' tool is clear through the explicit workspace-root 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?

Explicitly instructs the agent to call this tool first and explains the context: all other tools are scoped to these roots. It does not name a specific alternative or when-not-to-use case, but for a discovery tool this guidance is clear and sufficient.

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