load_liberty

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

No annotations provided; description only states loading and definition purpose. No mention of side effects, state changes, or required conditions. Minimal 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?

Single sentence is concise and front-loaded, but could be slightly more informative without losing brevity.

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?

Description lacks details on return values, error conditions, and file format. For a simple tool it is incomplete; agent may need to infer behavior.

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 lone parameter 'files' is not described in the description despite 0% schema coverage. No explanation of file paths, format, or expected count.

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 loads Liberty cell libraries and defines primitives for gate netlists. It is specific to Liberty format, but doesn't explicitly differentiate from sibling 'load_primitives'.

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 on when to use vs alternatives (e.g., load_verilog, load_primitives) or prerequisites. The description implies usage for Liberty libraries but lacks explicit context.

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