pytest

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only mentions that it runs pytest and returns the JUnit XML report, but omits details about side effects, exit code behavior, timeout potential, or any required environment setup, which are important for a test-execution tool.

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 filler. It is appropriately sized and front-loaded, conveying the core action and output format efficiently.

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?

Although the tool is simple and an output schema exists, the description leaves the `paths` parameter undefined and provides no context about test execution semantics or usage. This sparse description is insufficient for an agent to fully understand the tool's scope and potential side effects.

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 sole parameter `paths` has no description in the schema (coverage 0%) and is not mentioned in the tool description. While the name gives a hint, the description does not explain what paths should contain or how they are used, leaving the agent without sufficient parameter context.

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 ('Run') and resource ('pytest') and specifies the output format ('JUnit XML report'). It does not explicitly distinguish itself from sibling tools like basedpyright or ruff_lint, but its function as a test runner is inherently distinct from those linters.

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, nor any context about prerequisites or exclusions. It merely states what the tool does, leaving the agent to infer when it should be used.

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