search_render_report

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

The annotations already declare that this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description usefully adds that output goes to private state and that CSV/HTML are made safe via escaping, but it does not explain overwrite behavior, repeat-call effects, or what private state means operationally.

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?

It is a single compact sentence with no filler, which is good, but it is too terse for a report-writing operation and does not front-load the report-generation context. The sentence is efficient but under-structured for the task complexity.

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 described, but the description still omits key context: what report is generated, how the two optional IDs differ, and what happens when they are omitted. For a state-writing tool with two undocumented parameters, the definition is not complete enough.

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 zero description coverage for both audit_id and verification_id, and the description does not mention either parameter or explain their roles or relationship. The schema only supplies titles and regex patterns, so the agent receives no semantic guidance from the definition.

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 states a write action and names three output formats, but it never says what is being rendered or that the inputs identify an audit/verification report. The purpose is inferable from the tool name and sibling prefix, but the description alone is vague about the resource.

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 use this tool versus the search_* siblings, nor any prerequisites such as whether audit_id or verification_id is required. It only describes what is written, not the situation that calls for it.

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