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

The annotations state readOnlyHint=false, destructiveHint=false, and openWorldHint=false. The description adds real context on top: the write is additive feedback, it explicitly does not alter receptionist configuration, and it imposes a privacy constraint on payload content. It does not cover idempotency (what happens if the same call is reported twice) or failure modes, so it falls just short of a 5.

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?

Four short sentences, with the action and its precondition front-loaded, then constraints, then a scope disclaimer. Every sentence carries distinct information and nothing is repeated.

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?

With only two required params, full schema coverage, and no output schema, the description supplies everything an agent needs: purpose, sequencing after getCallDetails, payload privacy rules, and confirmation that no settings are affected. Nothing material is missing for correct invocation.

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%, and both callId and summary are fully documented in the schema, including the privacy rule on summary. The description restates the privacy constraint and signals that callId must come from a verified call, but adds little syntax or format detail beyond what the schema already provides. A baseline 3 is appropriate.

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 uses a specific verb and resource: 'Record one privacy-safe issue as negative feedback on a specific call'. It also scopes the operation to a single call and single issue, which separates it from any sibling that reads calls (getCallDetails, getCallHistory) or modifies the agent (updateAgent).

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?

It names the explicit prerequisite ('after getCallDetails provides concrete evidence'), the exclusion rule ('Do not include transcript quotes, caller details, or implementation internals'), and the boundary against a nearby class of tools ('does not change receptionist settings'). It gives the agent both when-to-use and when-not-to-confuse.

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