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

Annotations already cover the safety profile (not read-only, idempotent, non-destructive, closed-world), so the bar is lower. The description adds a real side effect beyond them: the ignore reason 'sharpens future ranking', plus the snooze default of 3 days and the requirement to include the posted link when replying.

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 the verb and resource before the four branch definitions, and no clause is padding. It is a single dense sentence with parallel dash/parenthetical structure, which is slightly heavy but still scannable.

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 and annotations carrying the safety profile, what an agent needs is status semantics, parameter-to-status mapping, and side effects — all present. Missing only peripheral details such as permission requirements or what the updated record looks like.

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 baseline is 3. The description goes further by mapping parameters to status branches in one view (posted_url with replied, reason with ignored, snooze with snoozed) and explaining the ranking consequence of reason, which the per-field schema text states only in isolation.

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 ('Record what happened') on a specific resource ('a Reddit, LinkedIn or X opportunity') and enumerates all four terminal states. This makes it unmistakable against siblings like draft_reply or list_opportunities, which read vs. produce replies rather than recording an outcome.

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?

The parentheticals define the condition for each status branch: replied means the user posted their answer, ignored means not a fit, snoozed means come back later, open means put it back on the board. That is genuine when-to-use guidance per value, though it never names an alternative tool or an exclusion.

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