Open Kioku Explain Test Coverage

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

Description discloses that the tool is read-only, does not execute tests, and reports only indexed data. This adds context beyond annotations (readOnlyHint=true, destructiveHint=false) by specifying behavioral traits like 'does not execute any tests'.

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?

Description is relatively concise and front-loaded, though repetitive in parts (first and third sentence overlap). Efficient overall.

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 presence of output schema, annotations, and sibling tools, the description covers purpose, usage, limitations, and return value types (coverage percentages, test file associations, suite metadata). Complete.

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 100%; description does not add significant meaning beyond schema for parameters. Baseline 3 is appropriate.

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?

Description uses specific verb 'Retrieve stored test-coverage evidence' and clearly identifies the resource: one file or whole repository. It distinguishes from siblings like recommend_validation_plan and find_tests_for_change.

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?

Explicitly states when to use the tool (inspect stored coverage) and when not to, providing alternative tools (recommend_validation_plan, find_tests_for_change).

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