Get My Profile

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

Beyond the readOnlyHint and openWorldHint annotations, the description reveals a significant behavioral nuance: it navigates to /in/me/ and resolves the redirect to obtain the real username, ensuring the url field returns the actual profile URL. This is valuable context that annotations do not provide.

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 compact and front-loaded, with the core purpose in the first sentence and the key behavioral detail in the second. Every sentence earns its place, with no tautology or redundant 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?

For a self-profile retrieval tool with an output schema and rich annotations, the description covers the essential nuance (redirect resolution) that could affect agent expectations. Parameters and return values are documented elsewhere, so nothing critical 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?

The input schema has 100% coverage with detailed descriptions for both 'sections' and 'max_scrolls', including examples and defaults. The tool description itself adds no parameter-specific details, so the schema carries the full burden. This matches the baseline for high schema coverage.

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's purpose: 'Get the authenticated user's own LinkedIn profile.' It uses a specific verb and resource, and the term 'own' distinguishes it from get_person_profile, which targets other people's profiles.

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 phrase 'authenticated user's own' implies it is for the current user rather than other people, providing clear context. However, it does not explicitly mention when to avoid using it or point to the sibling alternative get_person_profile, so some guidance is left implied rather than stated.

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