run_manufacturing_geometry_check

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

No annotations are provided, so the description carries the full burden of explaining behavior. The word 'profile' is ambiguous and does not disclose whether the tool runs a check, mutates state, requires an open document, or returns findings. It adds no behavioral detail beyond the name.

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, but this is under-specification rather than effective conciseness. It is a fragment that does not earn its place because it communicates almost no usable information.

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 is inadequate for a review tool among many similar tools. It does not explain the tool's scope, what 'manufacturing-geometry review' entails, whether a path is required, or what the returned profile contains.

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 0% description coverage, and the description does not mention the parameter at all. An agent gets no help understanding what path to provide or why it is needed.

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 is a noun phrase, 'Manufacturing-geometry review profile,' which restates the tool's domain but does not say what the tool actually does, what it checks, or what output it produces. It does not distinguish this tool from siblings like run_manufacturing_review or run_drc.

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 such as run_manufacturing_review, run_drc, or run_silkscreen_check. The description provides no context, prerequisites, or exclusions.

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