run_integration_tests_tool

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

With no annotations, the description must carry the behavioral burden. It only states the action and that a summarized result is returned, but does not disclose side effects, resource requirements, runtime expectations, or any potential impact on the project. This is minimal transparency for a test-running 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, succinct sentence that front-loads the core action and outcome. Every word is purposeful, with no extraneous information, making it appropriately concise.

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 (6 parameters, 4 required), lack of annotations, and absence of an output schema, the one-sentence description is far from sufficient. It does not explain how parameters interact, what the 'summarized result' contains, or any operational context. An agent would be unable to correctly invoke the tool without additional information.

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 description coverage is 0%, and the description does not explain any of the six parameters (projectId, commitSha, command, workingDirectory, regionId, framework). The description adds no meaningful information about parameter usage, formats, or valid values, leaving the agent without guidance on how to fill required inputs.

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 ('Run integration tests'), the resource ('for a project'), and the outcome ('return a summarized result'). This differentiates it from sibling tools like run_unit_tests_tool and run_mutation_tests_tool, making the purpose 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 explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The only clue is the phrase 'integration tests', which implies a use case but does not directly compare with sibling tools or discuss suitable scenarios.

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