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

The description warns that this 'bypasses structured rate limiting and can perform destructive actions', which directly conflicts with annotations declaring readOnlyHint=true, destructiveHint=false, and idempotentHint=true. An agent trusting the annotations would assume a safe idempotent read while the description describes a potentially destructive, unthrottled write path. This is a serious annotation contradiction.

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?

Three sentences with zero waste: purpose first, then method constraint, then the destructive/rate-limit warning, then the fallback rule. Front-loaded and appropriately sized for a high-risk escape hatch.

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 low-level open-world request tool with no output schema, the description covers the essential constraints and the risk profile. What it omits is what a raw call actually returns or how errors surface, and the behavioral picture it paints is at odds with the annotations rather than reconciled with them.

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 all five parameters (request_url, method, body, query_params, in_workspace) are already documented in the schema. The description only restates the GET/POST restriction already carried by the method enum, adding no extra parameter meaning. Baseline 3 applies.

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') plus the mechanism ('via Unipile's magic route'), and explicitly of the fallback nature relative to the other LinkedIn tools. An agent can identify this as the raw escape hatch without opening the schema.

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 an explicit when-to-use rule ('Use this only when no other LinkedIn tool covers the needed functionality') and a hard constraint (only GET and POST). This is a clear last-resort routing instruction against the many structured linkedin_* siblings.

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