Get My Profile

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

Annotations provide readOnlyHint=true, and the description adds valuable behavioral context: it navigates to /in/me/, resolves the redirect, and ensures the url field is the real profile URL. This goes beyond the annotation by explaining the scraping process and expected URL format.

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 two sentences: a concise purpose statement followed by a relevant behavioral detail. No wasted words, and the key info is front-loaded.

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 simplicity, the presence of an output schema, and thorough schema param descriptions, the description fully covers the essential behavioral nuance (redirect resolution) without needing to explain return values or parameter details. It is complete for its complexity tier.

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 schema has 100% description coverage for both optional parameters, so the baseline is 3. The description does not add parameter-specific meaning beyond the schema, but the schema itself is thorough.

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 retrieves the authenticated user's own LinkedIn profile, using a specific verb and resource. It also distinguishes itself from sibling get_person_profile by emphasizing 'own profile' and the /in/me/ redirect behavior.

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 makes evident when to use it (for the current user's profile) without explicitly naming alternatives. It does not say 'use get_person_profile for others', but the context of sibling tools and the 'authenticated user's own' phrasing provides clear usage context.

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