analyze_timing_closure

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

With no annotations, the description carries the full behavioral disclosure burden. It says the tool aggregates information into findings, but it does not disclose whether this runs analysis, blocks for a long time, requires existing run data, or has other side effects.

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 a single concise sentence with no filler and front-loads the main action and scope. It is appropriately short, though it sacrifices some useful detail for 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?

This appears to be a complex aggregation tool, yet the description provides almost no context about prerequisites, expected runtime, or how results relate to existing project state. The output schema may describe return values, but the description still lacks enough context for an agent to safely decide when to invoke it.

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, timeout_s, with 0% description coverage, and the tool description does not mention it at all. Although the parameter name hints at a timeout in seconds, the description adds no meaning beyond the schema and fails to compensate for the missing schema description.

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 names a specific action — 'aggregate' — and a clear resource scope: timing, constraints, methodology, DRC, and run messages. This distinguishes it from single-domain siblings like get_timing_summary or get_constraints_summary, though it does not explicitly name an alternative.

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 explicit guidance on when to use this tool versus the many related siblings. The aggregation wording implies a comprehensive analysis use case, but no preconditions, exclusions, or alternative routing are mentioned.

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