vbstudio_list_projects

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

With no annotations, the description carries the full disclosure burden. The [NOT IMPLEMENTED] status and 'Blocked' qualifier are critical behavioral traits that prevent an agent from making a doomed call. It doesn't describe return values or error behavior, but the non-functional status is the most important disclosure.

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 status flag front-loaded. Every word serves a purpose: what it lists, where, and its current limitation. No redundancy or filler.

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 stub tool with no parameters and no output schema, the description covers the essential facts: the intended operation, the blocking status, and the condition for unblocking. It lacks return format details, but since the tool is not yet usable, that's acceptable.

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, and schema coverage is 100%, so there is no parameter detail to add. The baseline of 4 applies because the description doesn't omit any parameter information; there simply isn't any.

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 action (list) and resource (VB Studio projects) with context ('on the instance'). It distinguishes from sibling tools like list_repos and vbcs_list_applications by the specific 'VB Studio projects' resource. The [NOT IMPLEMENTED] flag doesn't obscure the intended purpose.

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 'Blocked until a live dev instance is confirmed' provides explicit when-not guidance, telling the agent not to invoke the tool yet. It implies it should be used once the instance is available, but no alternative tools are mentioned, so it stops short of a full 5.

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