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

With no annotations provided, the description carries the full burden of disclosing side effects, and it explicitly does so with 'No sending, no cost.' This is a clear and valuable behavioral guarantee for an agent deciding whether invocation is safe and cheap.

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 one focused sentence that front-loads the core purpose and adds the crucial safety/cost information. Every phrase earns its place and there is no redundant 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?

The tool has no annotations, no output schema, and a parameter that is semantically opaque. While the description communicates the core preview behavior, it omits the meaning of the required id and gives no context about prerequisites or expected output, leaving too much for the agent to infer.

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 input schema defines a single required 'id' with no description, and schema description coverage is 0%. The description does not explain what entity 'id' refers to—whether it is a lead, recipient, agent, or LinkedIn account—so an agent cannot confidently determine the correct value.

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 names a specific action and resource: 'Render a sample LinkedIn connection request from this agent.' It also clarifies the non-sending nature, which distinguishes it from actual LinkedIn sending or connection tools. The title and description align and leave no doubt about what the tool produces.

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 gives no explicit guidance on when to use this tool versus alternatives like preview_linkedin_followup or connect_linkedin_account. 'No sending' implies a preview-before-send use case, but that is only implied and no alternative tools or exclusion conditions are mentioned.

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