p4_review

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

With no annotations, the description carries the full burden. 'List' clearly signals a read-only operation, which is helpful, but it does not disclose details like whether a workspace/current directory is required, what 'pending review' means exactly, or what the output looks like.

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 short and front-loaded with the core verb and object. It wastes no words, but it is also somewhat terse and could earn more depth without losing clarity.

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 tool with three optional parameters, no output schema, and many closely related siblings, a one-line description is insufficient. It does not explain the selection criteria, parameter roles, return format, or when this tool is the right choice.

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 already documents all three parameters at 100% coverage, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond the generic concept of listing pending changelists.

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 uses a clear verb and resource: 'List changelists pending review.' It identifies what the tool does without ambiguity, though it does not explicitly distinguish itself from related siblings like p4_reviews or p4_change_inspect.

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 given about when to use this tool versus alternatives such as p4_reviews, p4_review_prepare, or p4_change_inspect. The description is purely definitional and provides no context for choosing among the many related Perforce tools.

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