improve_test_coverage_orchestrator

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

No annotations are provided, so the description carries full burden. However, it does not disclose behavioral traits such as side effects (e.g., file modifications), authorization needs, or what constitutes 'prioritized next actions'. The description is too vague to inform the agent about consequences.

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, which is concise, but it sacrifices informativeness. It could be improved by adding key details without becoming overly long.

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 has 10 parameters, no output schema, and no annotations, the description is severely incomplete. It omits the iterative nature, convergence criteria, interaction between parameters, and the meaning of 'prioritized next actions'.

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 20%, yet the description adds no parameter details. It does not explain the role of any of the 10 parameters (e.g., targetLinesPercent, maxIterations), leaving the agent without guidance on how to populate them.

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 'Drive the full iterative coverage improvement loop and produce prioritized next actions' conveys a high-level process but lacks specificity. It does not clearly distinguish from sibling tools like ensure_coverage_setup or run_tests_with_coverage, which also cover parts of the loop.

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 is provided on when to use this orchestrator versus the individual sibling tools. There is no mention of prerequisites, alternatives, or context where this tool is appropriate.

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