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

With no annotations provided, the description carries the behavioral disclosure burden. It reveals meaningful scoping behavior: the required outreach scope and the visibility limitation for own-leads-only keys. This goes beyond the tool name, although it does not explicitly state read-only behavior or describe error conditions.

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?

The description is compact and information-dense. The first sentence states the core output, and the second sentence adds essential access-scoping context. Every part earns its place with no redundancy or 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?

For a parameterless read tool with no output schema, the description gives sufficient context: what the flags represent and the access constraints. It could be more explicit about the exact shape of the response or whether only flagged leads are returned, but overall it is adequate for an agent to invoke the tool 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?

The tool has zero parameters, so there is no parameter documentation required. The description adds context about scope and visibility that effectively substitutes for any parameter semantics, matching the baseline for parameterless tools.

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 clearly identifies the resource: current outreach lead-status flags for LinkedIn-DM leads marked as 'replied outside LinkedIn'. It avoids ambiguity and distinguishes this from mutation tools like mark_lead_replied_outside, though it lacks an explicit verb such as 'retrieves' or 'lists'.

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 conveys an important precondition: the outreach section must be in scope, and an own-leads-only key only sees its own conversations. However, it does not explicitly contrast this tool with sibling read tools like get_recent_leads or mention when to prefer one over the other, so usage guidance is implied rather than fully stated.

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