get_profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety and side-effect profile is fully covered. The description adds only the field inventory, which is arguably duplicated by the output schema. It does not clarify whose profile (authenticated user vs. arbitrary member) beyond the vague "the user's".

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 with zero filler, and the resource identification is front-loaded before the field list. Every word earns its place; nothing is repeated or padded.

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 a rich annotation set, a full output schema, and no parameters, the description covers what an agent needs to select this tool. The remaining gap is the ambiguity of "the user's" — nothing tells the agent this is the authenticated user's profile as opposed to a lookup keyed by an identifier.

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 are no parameter semantics to explain; baseline for zero-param tools is 4. The description's field list is a reasonable substitute for explaining what comes back, though it is largely redundant with the existing output schema.

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 pairs a specific verb ("Get") with a specific resource ("the user's basic LinkedIn profile") and enumerates the fields returned (name, headline, summary, location). It is unambiguous about what the tool retrieves; the small deduction is because it does not explicitly distinguish scope from siblings, though no sibling overlaps as a profile getter.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only implied by the resource name, which happens to be sufficient here because no sibling tool returns profile data. An agent must still infer that this returns the authenticated user's own profile rather than a given member's.

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