Get My Profile

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a non-obvious implementation trait: it navigates to /in/me/ and resolves a redirect so the returned url is the real profile URL. That is genuinely useful context an agent could not infer from schema or annotations. It stops short of mentioning rate limits, login/session prerequisites, or cost of the extra navigation.

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?

Two short sentences, front-loaded with the purpose and followed by the one behavioral nuance that matters. No filler or repetition of schema content.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. The redirect-resolution note fills the main gap; only the relationship to get_person_profile (and any session precondition) is left implicit.

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 coverage is 100%, with sections and max_scrolls fully documented in the schema, including enum-like section names and a reference to get_person_profile semantics. The description adds no parameter information, so the baseline 3 applies.

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?

States a specific verb and resource ('Get the authenticated user's own LinkedIn profile') and scopes it to the authenticated user, which cleanly separates it from the sibling get_person_profile that targets arbitrary people. An agent can select this without opening the schema.

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?

Usage is implied by 'the authenticated user's own profile', which suggests when to prefer this over get_person_profile, but the description never names that sibling or states an explicit when-to-use/when-not-to-use rule. Nothing tells the agent whether to use this first as a session/anchor step.

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