run_component_clearance_check

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It fails to mention side effects, return value, read-only versus mutating behavior, or any impact on the system. The term 'profile' is ambiguous and does not clarify whether this runs a check or returns static information.

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 short, which could be good for conciseness, but it is under-specified to the point of being unhelpful. It lacks the necessary content to be actionable, making it more of a placeholder than a concise description.

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 having an output schema, the description does not explain the tool's core purpose or behavior. For a tool with no annotations and minimal parameters, the description should provide substantial context but instead offers almost none. This is critically incomplete.

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 parameter 'path' with zero description coverage, and the description does not mention it at all. There is no explanation of what path refers to, how it affects the operation, or expected format. The description completely fails to compensate for the lack of schema documentation.

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 'Placement-clearance review profile' is vague and lacks a clear verb. It does not state what the tool actually does (e.g., runs, checks, generates). It merely rephrases the tool name without adding meaningful action or resource detail, and does not distinguish it from sibling review tools like run_thermal_review.

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?

There is no guidance on when to use this tool versus alternatives. No context, conditions, or exclusions are provided. The description gives no hints about appropriate scenarios or prerequisites, leaving the agent without any basis for tool selection.

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