run_testability_review

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

With no annotations, the description must fully disclose behavioral traits. It does not mention what the tool does (e.g., runs checks, generates reports), whether it has side effects, requires specific permissions, or how results are returned. This is a complete absence of behavioral transparency.

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 extremely brief (single fragment), but brevity here is under-specification rather than efficient conciseness. It lacks even a full sentence to convey the tool's purpose, making it too minimal to be useful.

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?

For a tool among many review siblings with one parameter and no annotations, the description provides almost no context. It fails to explain what testability review entails, how it differs from other reviews, or what the input path is for, making it completely inadequate for an agent to select and invoke correctly.

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 schema has one optional 'path' parameter with zero description coverage in the schema and no explanation in the tool description. The description does not clarify what 'path' refers to (e.g., file path, design path, project directory), leaving the agent unable to correctly set the parameter.

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 "Testability review profile." is a fragment that essentially restates the tool name without specifying an action. It does not clearly state that the tool performs a testability review or any specific verb+resource relationship, making it nearly tautological.

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 other review tools like run_thermal_review or run_manufacturing_review. The description neither suggests appropriate contexts nor rules out alternatives, leaving the agent without decision support.

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