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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds real value beyond them: the enumerated return payload, resume parse-state values (none/pending/parsed/failed), and the privacy guarantee about contact details and resume files. It omits edge behavior such as what happens when no profile exists or the user is unauthenticated, keeping it below a 5.

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?

Front-loaded with the core action in the first clause, then the return payload, then usage. The long field enumeration is justified because there is no output schema, though the resume-status parenthetical is slightly wordy relative to its importance.

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, the description compensates well by enumerating returned fields and resume status states. It lacks failure/empty-state behavior (no profile, not signed in, auth requirement), which an agent would need for a personal-data endpoint.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter semantics for a no-arg call.

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 and scoped resource: 'Get the signed-in user's own Levels.fyi career profile', then enumerates the returned fields (title, company, level, job family, focus area, location, YoE, skills, certifications, work history). No sibling tool overlaps with 'my own profile', and the 'Never returns contact details or the resume file' clause draws a clean boundary.

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?

Explicitly tells the agent when to use it: 'to personalize answers about the user's own pay, level or career.' It also states a scope exclusion (no contact details, no resume file). It does not name an alternative for adjacent needs (e.g. get-permissions, upload-resume for resume actions), so it stops short of full when/when-not routing.

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