Get my LinkedIn profile

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the concrete return payload (id, name, picture, email, locale), which is useful, but it omits behavioral context such as the requirement for a valid access token, what happens when unauthenticated, or any rate-limit/error behavior.

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?

A single sentence that front-loads the action and audience, then lists fields. No filler, no restatement of the tool name, and nothing extraneous.

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 zero-parameter read tool with no output schema, the description does the essential job by enumerating the returned fields, so the agent knows what comes back. It is only slightly short of complete because it says nothing about authentication failure modes or whether profile data may be partial.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The empty object schema is consistent with the description's claim that it implicitly operates on the signed-in member.

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 gives a specific verb ('Returns') plus a precise resource ('the signed-in member's basic profile from LinkedIn') and enumerates the returned fields. It is clearly distinct from write-oriented siblings like create_text_post or delete_post, though it does not explicitly contrast with auth_status, which arguably covers the adjacent identity-check space.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only weakly implied by 'signed-in member', leaving the agent to infer that this is the read path for the current user's identity rather than a validation or auth-state check.

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