company_kb_list_repositories

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates a read-only listing operation ('List... that have been synchronized'), reveals the local cache scope (not a live GitLab query), and specifies the types of metadata returned. This is sufficient transparency for a simple list operation, though it could optionally mention that no parameters are needed or that it requires an existing cache.

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 entire description is one focused sentence that front-loads the action ('List') and immediately specifies the resource and distinguishing scope. Every clause adds value: the local cache scope and the metadata fields are both essential and non-redundant with the tool name.

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 tool with an output schema, the description covers all necessary context: what is listed, the scope filter (synchronized repositories), and the key output components. It is fully adequate for an agent to select and invoke this tool correctly.

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?

The tool has 0 parameters and the schema is empty, so schema coverage is effectively 100%. The description does not need to explain parameters; the baseline of 4 for a zero-parameter tool applies, and the description adds no irrelevant 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 specific verb 'List' and a clear resource ('GitLab repositories that have been synchronized into the local RAG cache'), plus explicit detail about returned data ('local index counts and last sync metadata'). This clearly distinguishes it from sibling tools like company_kb_sync or company_kb_status, which focus on synchronization actions or status rather than listing cached repositories.

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 makes the intended context clear: it lists repositories already synchronized into the cache, implying this is the tool to consult when you need to know what is currently available locally. It does not explicitly name alternatives or state when not to use it, but the scope is specific enough that an agent can infer appropriate usage without confusion.

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