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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior: the call produces an outward-facing notification on the target member's side and consumes the daily visits quota. It does not state what the response contains, but the output schema exists, so this is only a minor gap.

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?

Three tight sentences: what it does, when to use it, and the routing rule to the sibling. The consequence (notification) and the cost (quota) are front-loaded rather than buried.

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 annotations covering safety/idempotency, a complete input schema, and an output schema for return values, the description supplies everything else an agent needs: the write-to-another-user side effect, quota cost, intended workflow position, and the alternative for read-only profile access.

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% and all three parameters (account_id, idempotency_key, linkedin_id_or_url) are documented in the schema, including target format and idempotency semantics. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 precise verb and resource ('Simulate a profile view') plus the externally visible consequence ('triggering a viewed your profile notification'). It explicitly names the sibling it is not (scrape_profile), so an agent can separate reading a profile from visiting it without opening either schema.

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?

Gives an explicit when-to-use ('leave a viewed your profile trace as a soft touch before an invitation') and an explicit when-not ('Not needed to read a profile, use scrape_profile' with a named alternative). The quota caveat further constrains when it is sensible to call.

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