view_profile

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

With no annotations, the description carries the burden and explicitly discloses that the operation is 'strictly read-only' and acts as the authenticated user. It doesn't cover edge cases such as private-profile visibility, but for a simple read operation this is adequate.

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 plus an Arg line and contains no filler. Every clause ('another', 'strictly read-only', 'as your authenticated user') carries signal.

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 a single-parameter read-only lookup, with an output schema present, so the description covers the input format and the operation's safety. Nothing required to invoke the tool correctly 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 schema only says 'Profile Url', so the description's clarification that the value can be a profile URL or vanity username adds meaningful input guidance. This compensates for the 0% 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?

States a specific action ('View another LinkedIn member's profile') with an explicit scope ('another', not your own), which distinguishes it from get_my_profile and search_people. The read-only qualifier further sharpens the intent.

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?

Indicates this is the tool for inspecting another member's profile as the authenticated user, and the 'another' framing implies get_my_profile is the alternative for one's own profile. It doesn't name sibling alternatives explicitly, but the context is clear enough.

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