report_methodology

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

With no annotations, the description carries the full behavioral burden. It does disclose the return shape ('violation list grouped by severity'), which is genuinely useful since there is no output schema, but it says nothing about read-only nature, whether an open/synthesized design is required, or how large the output can get.

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?

Two short sentences with the return shape front-loaded and no filler. The only waste is the redundant 'Run report_methodology' prefix that just echoes the name.

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 zero-parameter reporting tool the description is minimally adequate: it states the check family and the output grouping. It omits the state prerequisites (open project / synthesized design) that an agent would need to call it successfully, and no output schema exists to fill that gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. No parameter documentation is missing.

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 adds 'UltraFast methodology checks' and the return shape ('violation list grouped by severity'), which gives the agent more than the bare name. But the leading clause 'Run report_methodology' is a tautological restatement of the tool name, and it does not distinguish this from sibling report tools like report_drc, report_qor_assessment, or report_power.

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 run this versus report_drc or report_qor_assessment, nor any mention of prerequisites. The agent must infer that this belongs after synthesis or implementation from external Vivado knowledge.

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