BearQ: Run Tests in Functional Areas

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

Annotations indicate read-only, idempotent, non-destructive behavior, but the description says 'runs' which implies execution, potentially contradicting annotations. No additional behavioral context (e.g., async nature, duration, side effects) is provided beyond the minimal 'Toolset: Tasks' note.

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 short but includes an extraneous 'Toolset: Tasks' line. It front-loads the core purpose, but the extra line slightly reduces efficiency. Still, it is mostly concise.

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?

No output schema exists, yet the description fails to explain what the tool returns or how long operations take. Given the complexity of running tests, the description is incomplete for effective use.

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 documents the parameter with full coverage (100%). The description merely repeats that functional areas can be given by ID or name, adding no extra semantic value beyond schema.

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 runs regression test cases for specified functional areas, using 'run' as the verb and identifying the resource (test cases) and filter (functional areas). It helps differentiate from sibling tools like bearq_run_regression_tests (likely all tests) and bearq_run_test_cases (specific cases) by mentioning tagging with 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?

No guidance is provided on when to use this tool versus siblings, such as bearq_run_regression_tests or bearq_run_test_cases. The description does not specify prerequisites, expected contexts, or alternatives.

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