vts_p4

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It reveals that output is compacted/token-capped, that reconcile is forced to preview (-n), and that mutating commands are refused. This is good, though more detail on what 'compacted' means (e.g., how many tokens) could improve transparency.

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 four sentences, front-loaded with the main purpose, and every sentence adds essential information. No wasted words, clear and efficient.

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 tool's complexity (4 params, no output schema), the description covers what the tool does, which commands it handles, and what it refuses. It mentions output compaction and grouping, sufficient for basic usage. Lacks details on edge cases or error handling, but acceptable for a read-only wrapper.

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 coverage is 75% (maxResults lacks description). The description adds value by explaining output compaction and listing example subcommands, but does not directly link parameters like maxResults to compaction behavior. It adds some context but not enough to significantly enhance understanding beyond the schema.

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 runs a read-only Perforce command and compacts output, specifically mentioning subcommands like opened/status/reconcile/changes. It distinguishes from a raw p4 command, though not from sibling tools directly, but the purpose is specific and unambiguous.

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 explicitly advises when to use this tool ('Use instead of a raw `p4 opened`') and when not to use it ('mutating subcommands ... are REFUSED — run those directly'), providing clear guidance on appropriate usage.

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