get_insights

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., read-only, authentication needs, rate limits). The agent is left without information on side effects or constraints, which is critical for a data-fetching tool with no behavioral hints.

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 extremely concise (two words), but this brevity sacrifices informativeness. While concise, it is not well-structured or front-loaded with key information, earning a mid-range score.

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?

Given the high complexity (17 parameters, 6 enums, no output schema) and lack of annotations, the description is severely incomplete. It provides almost no contextual details, leaving the agent inadequately prepared to use the tool correctly.

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 0%, and the tool description adds no meaning to the 17 parameters. The schema provides patterns and enums but no explanations; the description fails to compensate, leaving the agent to guess parameter purposes.

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 'Fetch LinkedIn ads analytics' is a clear verb+resource but lacks specificity about the type of analytics or insights. It differentiates from sibling tools like get_ad_account and list_campaigns, but does not elaborate on the scope (e.g., performance metrics, demographics).

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?

No guidance is provided on when to use this tool instead of alternatives. For a tool with 17 parameters and many siblings, explicit usage context is missing, leaving the agent to infer from the name alone.

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