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

With no annotations, the description carries the full behavioral burden. It does disclose two useful traits beyond the schema: the call is metered ("1 credit") and it is conditional ("if found"), implying a possible not-found outcome. It says nothing about whether a failed lookup still costs credits, whether results are cached or how fresh they are, or what permissions/auth the call needs.

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 the action and the caller's input formats front-loaded, followed by the fields returned and the cost condition. No filler and nothing repeated from the schema.

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 one-parameter lookup with no output schema, the description does the important work of enumerating the return payload so an agent knows what it will get back. The remaining gap is operational: no annotation coverage means auth requirements, error/not-found semantics, and rate limits are left undocumented.

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 there is exactly one parameter, whose description already lists the accepted forms ("LinkedIn URL, slug or numeric/profile ID"). The description restates those accepted input formats without adding constraints such as example formats, normalization rules, or what happens with a malformed identifier, so the baseline 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 names a specific verb ("Get") and resource ("a person's professional profile") and enumerates the returned fields (name, headline, title, company, location, experience, education). The person-vs-company-vs-school split against enrich_company and enrich_school is implicit in the resource noun rather than stated, which keeps it just short of a 5.

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?

There is no explicit when-to-use guidance: nothing says when to pick enrich_person over search_people, or what to do when the identifier is ambiguous. The only usage-adjacent signal is the cost line "1 credit if found," which hints at a paid lookup but does not define the alternative paths an agent should consider.

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