qase_ci_report

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

The description discloses that the tool creates a run, records results, and optionally completes the run, adding behavioral context beyond annotations. Annotations indicate non-readonly and non-idempotent, consistent with the description. No contradictions.

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 two sentences long, with no wasted words. The first sentence states the primary function, and the second provides context and efficiency benefit. It is front-loaded and easy to parse.

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 6 parameters (3 required) and no nested objects, and an output schema exists, the description covers the high-level behavior well. It explains the single-call workflow vs alternatives, though it could mention return values or error scenarios.

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?

The input schema already has descriptions for all parameters (83% coverage based on context), so the description adds little on parameter meaning. The description does not elaborate on parameters beyond what's in the schema, so a baseline of 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?

The description clearly states the tool reports CI/CD test results in one call, replacing a multi-step workflow. It specifies the verb 'report', the resource 'CI/CD test results', and distinguishes from sibling tools like qase_result_record or qase_run_upsert by emphasizing the combined operation.

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?

The description explicitly says it is 'designed for CI pipeline integration' and replaces a manual 3-4 step workflow, providing clear context. While it doesn't explicitly list when not to use it, the intended use case is well communicated.

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