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

With no annotations, the description carries the full burden and does well: it discloses that output is drafts only and nothing is sent (safe/non-destructive), gives expected latency (~5 seconds), fixes the output cardinality at 3, and specifies inline return. It omits prerequisites such as whether LinkedIn credentials must be connected and what happens when no saved targets exist.

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 core behavior is front-loaded in a single strong first sentence, and the display template and do-not-chase constraints are actionable. The trailing '### Responses: **200**: Successful Response / Content-Type: application/json' block is raw OpenAPI boilerplate that adds no decision value.

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 no annotations, the description compensates well by fully specifying the returned draft fields and the required presentation format, so an agent knows exactly what to show. The remaining gaps are prerequisites (connected LinkedIn account) and failure/empty-target behavior, which matter for a pipeline invocation.

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?

Zero-parameter tool, so the baseline is 4; there is nothing for the description to disambiguate. The only missed opportunity is noting that targets are configured elsewhere rather than passed as arguments.

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+resource+cardinality: 'Draft 3 connection notes against the user's saved targets and return them inline in about 5 seconds.' 'Connection notes' implicitly separates it from run_commenting_pipeline and run_content_pipeline, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

Provides a clear when-not for follow-up tools ('Do NOT call approve_draft or schedule anything unless the user explicitly asks'), which is useful routing guidance. However, it never says when to pick this tool over discover_prospects, find_prospects, or draft_reply, nor how 'saved targets' are populated, so selection guidance is only partial.

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