linkedin_analyze_profile

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the analysis scope (which profile sections are examined), but says nothing about authentication requirements, whether external profile data must be fetched, side effects (though 'analyzes' implies read-only), or what the analysis output contains. A tool with zero annotation coverage needs more than this.

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 single tightly-scoped sentence with no filler. The core action and the analyzed content are front-loaded, and every word contributes meaning.

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?

The tool is simple (one parameter, no output schema, no annotations), but it sits among several ambiguously-similar siblings (research_profile, analyze_prospect, analyze_recent_activity). Without return-value information or usage boundaries, an agent cannot fully determine when this is the right tool or what it will receive back. The enumerated analysis scope helps, but significant gaps remain.

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% — profileId is already documented as 'LinkedIn profile ID or URL' in the schema. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies; the description neither compensates nor detracts.

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 has a specific verb ('Analyzes') and resource ('static profile'), and enumerates the exact components examined: headline, about, experience, skills, and business positioning. The word 'static' helpfully distinguishes it from sibling linkedin_analyze_recent_activity, though it does not delineate how it differs from similarly-named linkedin_research_profile or linkedin_analyze_prospect.

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 explicit when-to-use guidance or named alternatives. The term 'static' implies this tool is for a profile snapshot rather than activity streams, but the description never states when an agent should pick this over linkedin_research_profile, linkedin_analyze_prospect, or linkedin_analyze_recent_activity — a real gap given the 18 overlapping siblings.

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