vbcs_list_applications

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

No annotations are provided, so the description carries the burden. It indicates a read-only list operation ('List') and mentions the REST API with VBCS_BASE_URL, providing a prerequisite context. However, it does not disclose behavior such as pagination, authentication requirements, rate limits, or error handling, which could matter in practice.

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?

Two concise sentences, front-loaded with the core action and resource. The second sentence adds a critical scope qualifier without any fluff.

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 one optional parameter and no output schema, the description adequately covers the use case and key constraint. It mentions the REST API and VBCS_BASE_URL, and the standalone vs. git-backed distinction. It doesn't explain return format, but that's not required given the tool's simplicity.

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 schema covers 100% of the parameter (filter) with its own description, so the baseline is 3. The tool description does not add any extra meaning about how to use the filter parameter, deferring entirely to the schema.

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 lists applications on a standalone VBCS instance via its REST API, specifying both the resource and the method. It distinguishes from sibling tools like list_apps and list_repos by clarifying the scope: 'standalone VBCS instance' and 'not backed by a VB Studio git repo.'

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 gives clear context: use this for standalone VBCS instances, and explicitly states it is for apps NOT backed by a VB Studio git repo, implying alternatives exist. While it doesn't name the sibling tool (list_apps) directly, the exclusion is strong enough to guide selection.

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