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

Annotations already declare this a read-only, idempotent, non-destructive operation, so the description needs only to add behavioral context. It adds that the result is a timeline of experience categories and implies chronological ordering, but it does not explain whether the optional type parameter filters the timeline or how results are structured.

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 a single compact phrase that lists all relevant categories with no filler. The 'full timeline' qualifier is front-loaded and communicates scope efficiently.

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?

Given the simple optional enum parameter and comprehensive safety annotations, the description provides adequate basic context. It leaves out explicit filter semantics and return-value structure, which is a gap because there is no output schema, but the tool's simplicity keeps this from being severely incomplete.

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 description restates the enum values (employment, education, projects, certifications, awards) in prose, which partially compensates for the 0% schema description coverage. However, it does not clarify the effect of the optional type parameter (filter vs. select) or default behavior when omitted.

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 title and description clearly indicate this tool retrieves a complete experience timeline covering employment, education, projects, certifications, and awards. The resource is specific, but the description does not explicitly contrast it with sibling tools like get_project or list_projects, so it lacks explicit differentiation.

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 guidance on when to use this tool instead of alternatives such as get_project or list_projects. The phrase 'full timeline' implies comprehensiveness, but that connection is left to the agent to infer, and no exclusions or alternative triggers are stated.

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