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

Annotations only flag destructiveHint/readOnlyHint; the description goes well beyond by disclosing that it touches only the internal database and nothing on LinkedIn (invitation not accepted, ignored or withdrawn), that history is preserved, that confirm=true is required, and the exact return shapes (`forgot`, `found: false`). This is exactly the behavioral context a destructive tool needs.

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?

Front-loads the core action and the undo relationship, then layers constraints. It is dense but nearly every clause carries information; slightly long, but no wasted filler.

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 no output schema, the description still documents return values, the confirm gate, the data scope, and the ambiguity handling for multiple accounts — sufficient for an agent to invoke it correctly.

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 baseline is 3. The description adds value by clarifying the one-person/one-account addressing model and the confirm requirement, and by explaining the returned `forgot`/`found: false` semantics, though the per-parameter detail largely duplicates the schema.

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 with precise scope: 'Delete the triage decision recorded for ONE person on ONE account'. It explicitly contrasts itself with siblings (li_mark_invitations, li_received_invitations), so an agent can tell them apart without opening schemas.

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 explicit when-to-use ('the undo for a wrong li_mark_invitations') and a when-not-to/alternative ('To change a decision instead, just re-mark with li_mark_invitations'). The routing condition is unambiguous.

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