vast_list_tracking

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

No annotations are present, so the description must carry the full burden. It only states 'List all', but does not disclose that results are paginated via limit/offset, that 'all' requires iterating with offset, or what constitutes a tracking entry. This lack of behavioral detail could mislead an agent into assuming a single response contains every entry.

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, concise sentence with no redundant verbiage. However, it is under-specified in terms of content, though this is more a completeness issue than a conciseness flaw.

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?

With no output schema and no annotations, the description is too terse. It fails to mention that 'all' is subject to pagination, that offset can be used to retrieve subsequent pages, or what fields are returned in each tracking entry. This is a significant gap for an API that may return large datasets.

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 already provides descriptions for both limit and offset with 100% coverage, so the baseline is 3. The description adds no extra meaning beyond confirming the pagination parameters exist; it does not explain their relationship to the 'all' scope.

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 the resource ('all VAST tracking entries'), which unambiguously differentiates it from sibling tools like vast_get_tracking (fetch one) and vast_create_tracking. The scope 'all' is explicit.

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?

No guidance is provided for when to use this tool versus alternatives. While the name suggests listing, there is no mention of pagination behavior or contrast with vast_get_tracking for individual lookups. The description does not state any exclusions or prerequisites.

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