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

The description warns this 'can perform destructive actions' and allows POST, yet the annotations declare readOnlyHint=true and destructiveHint=false. This directly contradicts the structured safety profile an agent would rely on. The warning is useful in isolation, but the conflict is serious.

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?

Front-loads the capability, then the hard constraint, then the warning, then the routing rule. Every sentence earns its place, though 'Not available in this version' reads as a status note that could be clearer.

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 an open-world raw-request tool with 100% schema coverage and no output schema, the description covers capability, method limits, and routing. However the safety contradiction leaves an agent unable to trust the behavioral contract, which is the most critical thing for a tool that can mutate LinkedIn state.

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 description coverage is 100%, so the schema already documents all five parameters including the enum-restricted method. The description adds only the GET/POST restriction, which is already in the enum. Baseline 3 is appropriate.

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 and resource ('Send an arbitrary LinkedIn API request'), making the escape-hatch nature clear. It does not name or contrast with a specific sibling, but the generic-scope phrasing distinguishes it from targeted tools like linkedin_update_profile.

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?

Gives explicit routing guidance: 'Use this only when no other LinkedIn tool covers the needed functionality.' It clearly signals the when-not-to-use case but names no concrete alternative tool, leaving the agent to scan siblings itself.

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