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

No annotations are provided, so the description carries the full burden and does it: it declares the anonymity policy, that nothing is sent to LinkedIn, that no account state changes, that nobody replies, that the report cannot be followed up, the exact return payload, and the 422 rejection behavior with guidance on how to recover. This is far beyond what a bare mutation flag would convey.

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-loaded with purpose, then return contract, then use/don't-use, then arg guidance, then the privacy rule — a logical order an agent can scan. It is long and a few points repeat (the no-identifiers rule appears in the args block and again in the NEVER paragraph, and again in the schema), but every section earns its place given the privacy gate is a hard failure mode.

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 four-required-parameter write-ish tool with no annotations and no output schema, the description supplies the return value, the failure mode (422), the privacy contract, the sibling pre-check, and the routing rules. Nothing an agent needs in order to call this correctly or avoid calling it wrongly is missing.

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 baseline is 3, but the description adds real value the schema does not: the meaning of the three importance levels, the 200-character limit restated, a concrete worked example of an acceptable report vs. an unacceptable one, and the enumeration of forbidden identifier types (names, companies, @handles, draft_/chat_/prof_ prefixes). Only the frequency enum gets no extra gloss beyond what the schema already says.

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 ('send the Iridium team an anonymous note about something that broke') and immediately distinguishes it from the two things it could be confused with: a support ticket and a LinkedIn-side action. An agent can tell from the first paragraph exactly what this tool does and does not accomplish.

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?

Explicit USE THIS / DO NOT USE blocks with concrete triggering conditions ('tool failed, returned something wrong, or made a workflow the user cares about impossible to finish') and named exclusions (cap reached, LinkedIn disconnected, draft skipped — tell them instead). It also names the sibling list_solved_issues as a mandatory pre-check and gives the decision rule for what to do with its result.

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