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

Annotations already declare readOnlyHint, non-destructive, and closed-world behavior. The description adds return shape, status semantics ('needs_reconnect' blocks posting), and a security guarantee ('Never returns tokens'), though it omits details like pagination or rate limits.

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?

Purpose is front-loaded, then dense detail covers return fields, id conventions, status meaning, and downstream consumers. Most content earns its place, but nested parentheticals and long semicolon-separated clauses reduce polish.

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?

No output schema exists, so the description must explain return values; it does so with id, network, type, name, username/status, reconnect semantics, and token exclusion. This is enough for an agent to call and interpret the result correctly, with only minor omissions like ordering or pagination.

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?

With zero parameters, the baseline is 4. The description instead documents return fields and id formats, which does not add parameter meaning but is appropriate because no parameters exist.

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 ('Lists') and resource ('destinations') with scope ('this account may post to'). It enumerates network types, destination forms, and id conventions, so an agent can distinguish it from post/draft-oriented siblings.

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?

Explains that returned ids feed save_draft (any mix) and destination (LinkedIn id), which gives clear downstream usage context. It does not explicitly say when to call this tool versus alternatives or state exclusions, so it falls short of full when/when-not guidance.

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