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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses permission requirements, own-leads-only restrictions, idempotency, the unchanged:true return for already-marked leads, and the notification behavior for real changes.

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?

Three purposeful sentences packed with relevant information: the operation's effect, permission constraints, and idempotent side effects. No unnecessary filler or repetition of schema content.

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 two-parameter state-changing tool with no output schema, the description covers the essential behavioral outcomes, permissions, and edge case of repeated marking. An agent has enough context to call it correctly and to anticipate side effects.

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%, and the schema already documents both conversation_id and contact_name adequately. The description reinforces the general purpose but does not add significant parameter-level detail beyond 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 the exact action: marking an outreach lead as replied outside LinkedIn, with the concrete goal of stopping reports from flagging it as awaiting reply. This clearly differentiates it from sibling get_lead_status and unmark_lead tools.

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 description makes the usage context clear: use when a lead actually replied through email or phone rather than LinkedIn. It gives permission constraints but does not explicitly say when not to use it or name unmark_lead as the inverse alternative.

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