list_repos

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

With no annotations, the description must carry the behavioral burden. It clarifies the operation is local and scoped to VBS_WORKSPACE_DIR, which is useful. However, it does not disclose edge cases such as behavior when the directory is missing, whether subdirectories are scanned recursively, or any filtering of hidden/ignored repos.

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, front-loaded sentence that states the action and scope without unnecessary words. Every word earns its place.

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 zero-parameter listing tool, the description is largely sufficient. It clearly states what is listed and where. It could be slightly more complete by mentioning what is not included (e.g., remote repos, non-checkout directories), but given the simplicity, the current description meets most needs.

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 zero parameters, so the baseline is 4. The description naturally adds no parameter-specific semantics because there are none to describe. This is appropriate.

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: 'local VB Studio project repo checkouts discoverable under VBS_WORKSPACE_DIR.' This distinguishes it from siblings like list_apps and vbstudio_list_projects by specifying the local filesystem scope and environment variable.

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 implies usage for listing local repo checkouts, but it does not explicitly state when to use this tool versus alternatives like git_status or vbstudio_list_projects. No exclusions or alternative conditions are provided, leaving context to inference.

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