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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the explicit empty-state disclosure ('Empty if nothing is stored yet') tells the agent how to interpret a no-data result. It does not, however, describe scope restrictions or freshness of the memory.

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 content is front-loaded and delivered in essentially one dense sentence, with the higher-value empty-state note kept short. The trailing 'Args: {}' is redundant given the empty schema and the enumeration is long, but nothing is buried or circular.

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 need not restate return values, yet it helpfully summarizes the memory contents and the empty case. For a zero-parameter read tool it is nearly complete; the only gap is the absence of explicit when-to-use framing relative to upsert_career_memory.

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 tool takes zero parameters and the schema is an empty object at 100% coverage, so the baseline is 4. The description confirms 'Args: {}' but adds no further parameter meaning, which is appropriate since there is nothing to document.

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?

Uses a specific verb ('Get') plus the resource ('career memory') and enumerates exactly what is returned: target roles, locations, remote preference, seniority goal, industries, salary, work authorization, search stage, blockers, motivation, and free-form facts. This clearly distinguishes a read of career memory from siblings like upsert_career_memory or get_career_tips, though it never names the write counterpart as the alternative.

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?

The only routing guidance is a parenthetical noting that each free-form fact carries an id usable with forget_career_fact, which points at one downstream sibling but does not say when to call this tool versus alternatives. No explicit when-to-use or when-not-to-use condition is stated, leaving usage implied.

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