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

The description discloses important behavior beyond the annotations: the first check records a baseline and reports no changes; cached copies can be up to 90 days old without fresh=true; and fresh=true costs a paid lookup. These details align with readOnlyHint=false and give the agent essential execution context.

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?

The description is front-loaded with the core purpose, then covers input, alternatives, baseline behavior, and freshness rules in a compact form. Each sentence earns its place, and there is minimal redundancy.

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?

Although there is no output schema, the description provides enough behavioral context: what changes are detected, what a first check returns, how to ensure current data, and which sibling tool to use instead. This is complete for a tool with one required parameter.

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 schema already documents both parameters well, so the baseline is 3. The description adds extra meaning by explaining the 90-day cache staleness tied to fresh=false and by giving the username/URL input format and example context, which slightly exceeds what the schema alone provides.

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 uses a specific verb and resource: "Check one person's LinkedIn profile and report what has changed since the last check." It also names the explicit alternative search_linkedin_posts for posted content, which helps distinguish it from a key sibling tool.

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?

It explicitly says to use this for "watching a named person over time" and to use search_linkedin_posts for what they have posted. It also gives concrete scheduler guidance: set fresh=true when running as a scheduled watcher, because otherwise cached data may be up to 90 days old.

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