Get profile snapshot

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

No annotations are provided, so the description carries full burden. It discloses that files are written locally and nothing is sent to LinkedIn (risk: local-write). However, it lacks details on what exactly is written (e.g., file format, location, overwrite behavior) and whether the tool returns a status or path. This is adequate but not thorough.

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 a single paragraph, front-loaded with risk and purpose. It efficiently conveys essential information without extraneous text. Every sentence contributes to understanding.

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 tool's complexity (3 parameters, nested JSON, no output schema), the description is incomplete. It does not explain what the tool returns after processing (e.g., a confirmation, file path, or snapshot ID). For a file-writing tool, this is a notable gap. The behavior for different sources is described, but the output is missing.

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%, providing a baseline of 3. The description adds value beyond the schema by explaining each source enum value (e.g., 'raw copy/paste from your profile page' for pasted_text) and clarifying that the json parameter expects a 'Structured profile' and text parameter is for pasted/PDF text. This enhances understanding.

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 clearly states the tool writes files locally to ingest LinkedIn profile data from various sources (pasted text, PDF text, structured JSON, or load saved). It distinguishes from siblings like audit_profile or rewrite_experience, which modify or analyze data, making the purpose unambiguous.

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?

The description lists four source types and explicitly says 'No scraping; you provide the data,' implying it should be used when a user has profile data to import. Although it doesn't directly contrast with siblings, the context suggests using this before other profile-related tools. No explicit 'when not to use,' but still clear.

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