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

With no annotations, the description carries the full burden. It usefully discloses that results default to the top 5 recent runs and warns against env scoping, but omits read-only confirmation, permission requirements, pagination behavior (limit/offset exist in schema), and the shape of returned history entries.

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?

Three dense sentences, front-loaded with the primary input modes before the optional narrowing parameters. No filler, though the coverage-comparison clause ('as for coverage') is slightly cryptic for an agent without external context.

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?

For a 10-parameter tool with nested objects, no annotations, and no output schema, the description covers the selection-relevant parameters but leaves limit/offset/release unexplained and says nothing about what a history record contains. Adequate but with clear gaps.

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% across 10 params, so the description must compensate, and it does for most: testId, scenarioId, environment, branchName, scope.filePaths, platform, and dimensionFilters. It leaves limit, offset, and release entirely unaddressed, which keeps it from a 5.

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 names a specific verb (Fetch) and resource (SmartTest execution history) and lays out three distinct input modes: testId, folder/file scope, or scenarioId. It references the sibling fetch-execution-report as the source of testId, giving partial differentiation, but does not contrast its own output with that sibling.

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?

Explicit routing advice: 'Prefer testId when you have it from fetch-execution-report' and 'Typically omit environment to avoid env scoping.' It also points to branchName/scope.filePaths usage 'as for coverage.' No explicit when-not-to-use-this-tool statement, so not a 5.

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