rag_source_roots_list

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

No annotations are provided, so the description carries the full burden of disclosing side effects. It mentions optional syncing of newly added configurations/extensions but does not state whether sync modifies persistent state, requires permissions, or can be undone, nor how it interacts with the default sync=true value.

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 a single sentence with the primary list action front-loaded and the optional sync behavior appended. It is concise and easy to parse, though the dual behavior slightly reduces sharpness.

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 list tool with an output schema and no required parameters, this is minimally viable. However, it omits usage guidance, session semantics, and the practical distinction from related RAG listing tools, leaving meaningful gaps for agent selection.

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 explain both parameters. It partially explains 'sync' by tying it to 'sync newly added configurations/extensions', but 'session_id' is left entirely to its name and default value.

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 names a specific action ('List') and a specific resource ('RAG source discovery roots'), and it previews the optional 'sync' behavior. It distinguishes this tool from siblings like rag_sources_list by focusing on roots, though it does not explicitly call out the distinction.

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?

There is no explicit guidance on when to use this tool versus alternatives such as rag_sources_list or rag_sources_add_from_directory. The context is implied by the name and wording, but no exclusions or decision criteria are given.

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