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

Annotations already declare a non-read-only, non-idempotent, non-destructive write, and the description adds genuinely useful context: the required sign-in flow, that re-recording the same regulation+pinpoint overwrites, and that assessments are annotations that never suppress search/read results. It stops short of describing what the overwrite does to audit history or what the call returns, but it is well above the annotation baseline.

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?

Dense but front-loaded: the auth prerequisite comes first, then the core action, then the enum/overwrite semantics. Nearly every sentence carries a distinct constraint; the enum restatement in the description is the one mildly redundant element.

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 6-parameter (all-optional) write with no output schema, the description covers trigger, auth, overwrite behavior, and value constraints. The only gap is that with no output schema present, the description says nothing about what a successful recording returns or how the write is confirmed.

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 coverage is 100%, so the verdict and reason enums are already documented in the schema and the description mostly restates them. It does add one real constraint — reason must be a structured code, never free text — and ties trial_id/session back to connect, but this is marginal value over structured fields, so 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 verb and resource — 'Record one structured applicability verdict on a regulation pinpoint' — and scopes it to a keyless trial_id. An agent can immediately distinguish this write from read-side siblings like list_assessments or search_regulation.

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 clear trigger ('Call after the officer states applicability') plus a hard prerequisite (connect/connect_verify sign-in) and an exclusion (reason codes only, never free-text notes). It does not name a specific alternative tool for the 'don't record' case, but 'assessments annotate; they never hide search or read results' effectively clarifies the boundary.

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