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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds that selection draws from relatedTests/taggedTests/suiteCandidates and can be constrained, but it does not explain the selection algorithm, precedence among sources, or output shape. With annotations present, this is minimum viable.

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 definition is a single front-loaded sentence with no filler text. The dense parenthetical parameter list is slightly compressed but still readable and 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?

The tool has 11 parameters, no required parameters, low schema description coverage, and no output schema. The description does not explain return shape, selection logic, or how the optional constraints affect the chosen subset, leaving the definition incomplete for this 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 description coverage is only 18%, and the description merely names six parameters plus three source arrays. It does not define how includeTags, suitePercentage, maxTests, maxTimeBudgetMins, branchName, or environment interact, nor how the candidate sources are combined or prioritized.

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?

States a specific verb ('Select') and resource ('SmartTest smoke subset') and identifies the candidate sources and optional knobs. It does not explicitly differentiate from sibling tools or clarify when this selection is preferred.

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 when-to-use guidance or alternatives are provided. The description only lists optional inputs, so an agent cannot tell from it when to choose this tool over list/get-style siblings.

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