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

Annotations cover safety (readOnlyHint, openWorldHint), and the description adds real behavioral detail beyond them: masked fields are dropped rather than returned as asterisks, and each call costs 1 credit. These are exactly the non-obvious traits an agent needs before invoking. The only gap is caching behavior, which is left implicit even though a cache_max_age parameter exists.

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 with the key constraint (masking) and cost up front, and no filler. The lead sentence 'Person's profile.' is redundant with the title but wastes only a few words.

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 no output schema, listing the returned fields and the masking rule is the right compensation, and the cost disclosure is valuable for a metered API. The remaining hole is cache_max_age, which neither schema nor description explains.

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?

At 50% schema coverage the description should compensate for undocumented parameters, but it says nothing about inputs. The url parameter is documented in the schema, yet cache_max_age is described nowhere and its semantics (staleness window, format) remain unknown to the agent.

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/resource combination (fetch a LinkedIn member's public profile) and enumerates the returned fields (name, headline, location, followers, avatar, employers, education). However, the opening sentence 'Person's profile' merely restates the title, and nothing distinguishes it from siblings like linkedin_company or linkedin_searchPosts.

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 when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The phrase 'logged-out profile' hints that no authentication is involved, but the agent must infer that; there is no routing instruction toward linkedin_company or linkedin_searchPosts.

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