vast_get_companion

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

With no annotations provided, the description carries full behavioral burden. It only says 'get details', implying a read operation, but does not disclose any side effects, permission requirements, or error behavior (e.g., if the ID does not exist). No meaningful behavioral context is added beyond what the tool name already implies.

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 with no redundancy or filler. It communicates the core operation efficiently, making it concise and well-structured.

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 get-by-ID tool, the description is adequate in some respects, but it critically lacks disambiguation between the vast_ and vast42_ tool families. This omission could lead an agent to invoke the wrong endpoint. While no output schema exists, the description should still clarify the VAST version and relationship to siblings, which it does not.

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 input schema has 100% description coverage for the single 'id' parameter, which is documented as 'VAST companion ID'. The description adds no further explanation of the parameter or its format, but with full schema coverage, the baseline of 3 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 states the tool gets details of a VAST companion, which is a clear verb+resource. However, it fails to distinguish from the similarly named sibling tool vast42_get_companion; 'VAST companion' could refer to either the VAST or VAST42 resource family. This ambiguity makes it less effective for agent selection.

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 provides no guidance on when to use this tool versus alternatives like vast42_get_companion or vast_list_companions. It does not mention that the 'id' parameter is required, nor any preconditions or version-specific context.

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