linkedin_profile

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

With no annotations, the description must carry the full behavioral burden; it does convey that this is a read operation scoped to the current session ('signed-in member'), implying auth dependency. However, it says nothing about behavior when no member is signed in, whether the call has side effects, or any rate limits.

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 front-loaded sentence with no filler; the verb, scope, and returned fields are all present in one pass.

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-only tool with no output schema, the description is nearly sufficient because it enumerates the returned fields (name, email, picture, member id) and names the auth scope. The only gap is not describing failure behavior when unauthenticated.

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 the baseline is 4. The description usefully identifies the data source (the signed-in member's OpenID profile) rather than accepting an arbitrary member id.

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 (Read) and resource (the signed-in member's OpenID profile) and enumerates the returned fields, so the agent knows exactly what it produces. It does not explicitly differentiate itself from siblings like linkedin_status, but the read-only profile scope is unambiguous.

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 'signed-in member' implies the prerequisite that a login must already be established, which is useful context, but it never states when to call this versus linkedin_status or linkedin_login. Usage is 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.