Report Set Info

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

With no annotations, the description carries the full behavioral burden, yet it only implies mutation via 'Update'. Critically, every parameter defaults to null and the description never says whether null means 'leave unchanged' or 'clear the field' — a decisive ambiguity for a mutation tool.

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?

A single short sentence with no waste, but it is terse to the point of under-specification rather than efficient — the brevity removes needed information rather than improving navigability.

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?

An output schema exists, so return values need not be explained, but for a 7-parameter mutation tool with no annotations and no per-field documentation, the definition leaves an agent guessing about scope, partial-update semantics, and which call site is appropriate.

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?

Seven parameters at 0% schema coverage, and the description only gestures at 'conclusion' (matching one parameter) and vaguely 'header fields'. dut, setup, title, project, engineer, and description are undocumented in both schema and prose.

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 specific verb+resource: 'Update report header fields / overall conclusion', which tells an agent this touches report metadata rather than items or notes. It does not explicitly name or differentiate itself from siblings like report_edit_item or report_add_note, so it stops short of a 5.

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 when-to-use guidance, no prerequisites, no alternatives named. An agent cannot tell from the description whether this should be called before report_start, during an open report, or instead of report_edit_item.

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