Test Case Üret

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description is not required to restate it. The description adds the 'standard' qualifier, implying normalized/consistent output, which is a modest addition beyond the annotations. No contradiction exists — 'generate' aligns with read-only generation.

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?

A single declarative sentence with zero filler. The purpose is front-loaded and every word earns its place. It is efficient without being under-specified to the point of tautology.

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 presence of an output schema covers return-value expectations, so that gap is handled. However, with six parameters and zero schema description coverage, the description leaves four parameters (module, risk_level, include_boundary, include_negative) undocumented. An agent would struggle to configure generation correctly without additional guidance.

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%, so the description must compensate, but it only implicitly references two of the six parameters (feature and acceptance_criteria). module, risk_level, include_boundary, and include_negative are entirely unexplained in both the schema and description, leaving the agent to guess their meaning and interaction.

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 states a specific verb ('üretir'/'generates'), a specific resource (standard test cases), and the source inputs (feature description + acceptance criteria). This clearly distinguishes it from the sibling tools, which are about linting, normalizing, converting to Xray, composing suites, or reporting coverage rather than generating.

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 phrase 'from feature description and acceptance criteria' implies the generation scenario, but the description never explicitly routes the agent — it does not state when to use this tool versus alternatives or when not to use it. No sibling is named and no exclusion condition is given, leaving selection to inference.

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