generate_report

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether an existing file at output_path is overwritten, whether the analysis must be solved first, or whether the tool blocks/fails on bad input. Listing the arg names is not behavioral disclosure.

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?

One short sentence plus an arg list, with the purpose front-loaded and no filler. The 'Args:' fragment is terse to the point of under-specification rather than verbose, so brevity is not the problem here.

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 3-parameter tool with zero annotations and 0% schema coverage, this description leaves too much unspecified: overwrite behavior, prerequisites (a solved analysis), and analysis_index meaning are all absent. An output schema exists, so return values need not be explained, but the invocation-side gaps remain.

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?

Schema description coverage is 0%, so the description must compensate; it does add genuine value by enumerating the fmt values ('docx or txt'), which the schema does not (no enum present). However, analysis_index is unexplained (which analysis? what does the default 0 select?) and output_path's required format/extension expectations are not stated.

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?

States a clear verb+resource ('Generate simulation report'), which no sibling tool duplicates — the sibling list contains only model/mesh/BC/solve operations. It does not need sibling differentiation here, but it also does not mention scope (single analysis vs whole model), leaving one gap.

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 when-to-use guidance at all — nothing says this should be called after solve_analysis, nor whether it is restricted to a completed/solved analysis. No exclusions or alternatives are named, so the agent must infer usage from context alone.

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