run_full_automation

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

With no annotations, the description must disclose behavior. It mentions 'hybrid' mode and a pipeline, but doesn't explain what 'execute' does (mutations?), whether it modifies files, requires auth, or has side effects. The agent cannot infer the operational impact from this description.

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 extremely short, but not appropriately sized for a complex tool. While concise, it sacrifices essential information. The structure is a single sentence with arrows, but it's not informative enough to be effective.

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?

The tool has 6 parameters, no output schema, and 22 siblings, yet the description is a one-liner. It doesn't mention return values, errors, or how it integrates with the rest of the workflow. Completely inadequate for the complexity.

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 has 6 parameters with zero description coverage, and the tool description provides no parameter information. The agent must rely on names alone (e.g., 'autoFix', 'confirmMode') with no explanation of semantics, defaults, or relationships. This is a critical gap.

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 lists a sequence of actions ('Analyze → plan → execute → detect → suggest') but fails to specify the actual output or resource. It's unclear what 'full automation' entails and how it differs from sibling tools like run_scenario_test or suggest_fixes. This is more of a process description than a purpose statement.

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 on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or scenarios where a more targeted tool would be preferable. The description only implies a one-call pipeline without contextual cues.

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