vca_info

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Get' implies a read-only operation, and it specifies the returned fields (guid, name, volume in dB), but it does not explicitly state permissions, error behavior, or side effects. This is adequate but not rich, warranting a mid-range score.

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 extremely concise: one sentence stating the purpose and a single line for the argument. No filler or redundant information, making it efficient and front-loaded.

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 read tool with one parameter and no output schema, the description covers the key return values (guid, name, volume) and the target format. It does not address potential errors or invalid targets, but given the low complexity, it is largely complete. Slightly more detail on edge cases could push it to 5.

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 description coverage is 0%, so the description must compensate. It explains that 'target' accepts a vca:/ path or a {guid}, adding meaningful context beyond the raw schema. This sufficiently clarifies the parameter format, though it lacks examples or edge-case details.

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 retrieves a VCA's guid, name, and current volume in dB, which is a specific verb+resource combination. It distinguishes from siblings like vca_list (likely lists all VCAs) and vca_volume (likely alters volume) by focusing on read-only info retrieval.

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 (to get details of a specific VCA), but does not explicitly state when to use it over alternatives like vca_list or vca_volume. There is no mention of exclusions or alternative tools, so it falls at 'implied usage' rather than explicit guidance.

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