pip_version

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

The description discloses the return format (dict with status, exit_code, stdout, stderr, output, duration_ms), which is helpful behavioral context. However, it does not mention potential side effects, permission requirements, or error conditions, and annotations are absent so the description carries the full burden. This is partially transparent but lacks deeper explanation.

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 very concise and front-loaded: a single sentence for purpose, followed by a structured return format and an example call. Every element earns its place, with no unnecessary fluff. The example is useful for immediate invocation.

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 simplicity (no parameters), the existence of an output schema, and lack of annotations, the description fully covers the essential information: what it does, what it returns, and how to call it. The return format is even specified in prose, making it self-contained. No crucial gaps remain.

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 tool has zero parameters, so the schema is empty. Per rubric, 0 params gets a baseline of 4. The description adds no parameter information because there is nothing to document, which 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 clearly states 'Return the current pip version' with a specific verb and resource. It distinguishes itself from sibling version tools like python_version and node_version by explicitly naming pip. The purpose is 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 provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions or compare with sibling version tools. The intended usage is only implied by the tool name, not explicitly stated.

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