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

Annotations already mark this as non-read-only and idempotent, and the description complements them by disclosing the external side effect: the target member receives a 'viewed your profile' notification. It also clarifies the operation is a simulation, which is meaningful behavioral context beyond the schema. It does not contradict the annotations.

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?

One sentence with no filler. The primary action and the key side effect are front-loaded, making the tool's purpose immediately understandable.

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 single-purpose action with a complete input schema, meaningful annotations, and an output schema, the description covers the essential behavior. It could mention caveats like notification visibility or rate limits, but nothing critical is missing for invoking the tool correctly.

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 description coverage is 100%, so the input schema already documents all three parameters. The description adds little beyond the schema, mostly reinforcing that the target is a LinkedIn member. With full schema coverage, a baseline of 3 is appropriate.

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 states a specific action ('simulate a profile view') and its observable consequence ('triggering a 'viewed your profile' notification'). It is clear about the resource being acted on, but it does not explicitly distinguish itself from siblings like scrape_profile or profile_viewers, so it misses the top score.

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 description gives no guidance on when to use this tool instead of alternatives, when not to use it, or how it fits into a workflow. An agent must infer from the name and wording that this is for simulating a visit rather than actually performing one.

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