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

No annotations are provided, so the description must disclose behavioral traits. It says nothing about what the tool does, what data it returns, whether it is a read operation, or any side effects. The description sheds zero light on behavior.

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?

A one-word description is under-specification, not conciseness. It is too terse to be useful, and while there is no waste, it fails to convey necessary information.

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?

Despite the tool having only one parameter, there is no output schema, no annotations, and the description explains nothing about return values, expected behavior, or use cases. The description is practically empty and inadequate for an agent to understand the tool.

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 has 100% coverage; the parameter 'url' is described as 'LinkedIn profile URL'. The baseline of 3 is appropriate because the schema documents the parameter, even though the tool description adds no parameter-related meaning.

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 is simply 'LinkedIn' - a noun naming the platform, not a description of what the tool does. It does not state any verb or resource beyond what the tool name already implies. It is effectively a tautology and gives no specific functionality.

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?

There is no guidance on when to use this tool versus the many similar scrapecreators_* tools. No context, no exclusions, no mention of alternatives. The user is left without any information about the intended use case.

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