BearQ: Refine Tests in Functional Areas

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

The description states 'Refines' implying modification, but annotations set readOnlyHint=true, creating a direct contradiction. Per scoring rules, contradictory descriptions receive a score of 1. The mention of multiple passes is additional but overridden by the contradiction.

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 concise (three sentences) and front-loaded with the primary purpose. Every sentence adds value: purpose, parameter clarification, and behavioral note about multiple passes. No unnecessary words.

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?

Despite good conciseness, the description is incomplete given the contradictory annotations. It does not explain what 'refine' entails, success criteria, or output. The tool lacks an output schema, so the description should compensate. The contradiction further degrades completeness.

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 coverage is 100% for the single parameter. The description notes that functional areas can be given by ID or name, which matches the schema description. No additional semantic value is added beyond what the schema provides.

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 action (refines) and the resource (draft test cases) with a specific scope (tagged with functional areas). It effectively distinguishes this tool from siblings like bearq_refine_all_draft_tests by scoping to functional areas.

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 implies when to use the tool (when you need to refine draft tests by functional area) but provides no explicit guidance on when not to use it or alternatives. It does not mention sibling tools or conditions for avoiding this tool.

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