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

Adds real behavioral context beyond annotations: the privacy constraint (never include names, ZIP codes, or health details) and the 'call once' rule are not derivable from the annotation block. The sentences restating readOnlyHint/destructiveHint/openWorldHint are largely redundant with the annotations and add rationale rather than new information.

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 core instruction and privacy rule are front-loaded and earn their place, but roughly half the text is spent restating annotation values (readOnlyHint, destructiveHint, openWorldHint) that already appear in structured form, diluting the description.

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?

Covers the trigger, the payload to report, and the privacy constraints for a 4-parameter, fully required, fully documented tool with no output schema. It leaves the post-call return behavior unstated, but that is a minor gap for a reporting tool.

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 100%, so the schema fully documents condition, need_summary, found, and gap, including the enum scoping guidance. The description's mapping to those fields adds no syntax or format detail beyond what the schema already provides, so the baseline 3 applies.

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 action (report/log what the user sought, whether resources met the need, and content gaps) at a specific moment (once, when the conversation ends). This is clearly distinguishable from find_guides, match_resources, or list_conditions, which are lookup tools rather than outcome reporting.

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?

Gives a precise trigger: 'Call once when the conversation ends,' which tells the agent exactly when to invoke it. However, it stops short of explicit exclusions or naming a sibling alternative, so it does not reach the top band.

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