Run a compact multi-step validation plan

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

Annotations provide no safety hints beyond non-destructive. The description adds that it is a local call returning compact summaries, which is helpful. However, it does not disclose behavior on failure, required permissions, or whether it modifies files. Given no annotation burden, the description adds minimal extra context.

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 sentence of 23 words, efficiently communicating the core functionality without any fluff or repetition.

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 complexity of 8 parameters and the combined nature of the tool, the description is too sparse. It does not explain the different validation profiles, what each validation entails, or the format of step summaries. With no output schema, the description should provide more context but fails to.

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 only 25% and the description provides no parameter explanations. It does not help the agent understand parameters like 'profile', 'npmScripts', 'stopOnFailure', etc., which are crucial for correct usage.

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 it runs Git diff checks plus selected Composer, Laravel test, and npm script validations in one local call, returning compact step summaries. It distinguishes itself from individual sibling tools like run_tests or run_npm by emphasizing the multi-step aggregation.

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 implies usage for efficient multi-step validation ('reduce round-trips'), but does not explicitly state when to use this tool versus running individual validations separately, nor does it mention prerequisites or exclusions.

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