Find RAG workspace for a repo

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

With no annotations provided, the description carries the behavioral burden itself. It discloses that this is a non-mutating existence check, that matching is exact, and it explicitly describes the returned shape ({exists, workspace|null, all}). It does not state auth requirements, but for a simple existence check the core behavior is transparent.

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 three short sentences that front-load the main action, then add matching semantics and return shape. Every sentence contributes useful information with no padding.

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?

Given the low complexity, single parameter, and absent output schema, the description covers the important return contract and matching behavior. It does not tell the agent when this should be used over sibling tools, but the tool itself is simple enough that the omission is not fatal.

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%, so the schema already documents the `name` parameter. The description adds the useful detail that matching happens against the exact display name, which slightly enriches the schema semantics, but it mostly restates the parameter example rather than introducing substantial new meaning.

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 clearly states the tool checks existence of an AnythingLLM workspace for a repo, and names the exact matching behavior. It is distinct enough from the creation/search/write/forget siblings, though it does not explicitly name a sibling or call out the difference from rag_search.

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 guidance on when to use this tool rather than rag_search or rag_create_workspace, and no mention of prerequisites or fallbacks. The reader can infer it might be useful before creating a workspace, but that is not stated.

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