vast42_get_non_linear

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the get operation without any additional context such as return format, error behavior, authentication requirements, or side effects. This is a minimal disclosure that adds no behavioral transparency beyond the purpose itself.

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, focused sentence that is front-loaded with the key information. Every word is meaningful and there is no redundant phrasing. It is appropriately concise for a simple get-by-ID operation.

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?

Given the absence of an output schema and annotations, the description should provide some context about the return value or behavior. It only states the operation, leaving the agent unsure of what the response looks like. Additionally, the existence of a similar sibling tool (vast_get_non_linear_media) is not addressed, creating potential confusion. The description is minimal but lacks necessary context for a reliable tool invocation.

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 covers 100% of parameter descriptions (id is defined as 'VAST 4.2 non-linear media ID'), so the description does not need to add parameter details. The description does not conflict with the schema, but does not add extra semantic value beyond what the schema already provides.

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 verb 'Get' and the specific resource 'single VAST 4.2 non-linear media', distinguishing it from list, create, update, and delete siblings. It precisely identifies the operation and resource.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention sibling tools like vast42_list_non_linears or vast_get_non_linear_media, nor does it provide any exclusions or prerequisites. The usage context is entirely implied by the tool name.

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