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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is fully covered. The only behavioral addition is the 'newest first' ordering, which is genuinely useful but thin; nothing is said about pagination, completeness of history, or how missing highlights/technologies are represented.

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 dense sentence with the primary content front-loaded and the returned fields enumerated after; no filler, no repetition of annotation facts.

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 an output schema present, the description needn't explain return structure, and the annotations cover safety. What remains is a small gap: it does not acknowledge the optional kind/lang filters or clarify whether the list is the complete history or a truncated view.

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 coverage is 100%, so both the kind enum and lang default are already fully documented in the schema. The description's phrase 'work history and education' hints at the default both-kinds behavior but adds no detail on the lang filter or the shape of the kind switch — 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 the resource content precisely — work history and education, with role, period, summary, highlights and technologies — which lets an agent distinguish it from get_skills and get_profile. It lacks an explicit verb, relying on the name 'get_experience' to convey retrieval, but the scope is unambiguous.

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?

Usage is only implied: an agent can infer this is the tool for career/education history, but nothing states when to prefer it over get_profile or get_skills, nor that it can be narrowed to just work or just education. No exclusions or prerequisites are given.

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