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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it discloses the returned content structure (including the problem/part/approach/outcome/metrics/media breakdown for projects) and the computed fields, and it explains the side effect of supplying `criteria` (an evidence map is added). No auth or scoping notes, but the behavioral picture is solid.

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?

Two sentences, front-loaded with the resource and its contents; the parenthetical field breakdown is dense but informative rather than redundant. The only cost is that the long enumeration makes the first sentence heavy, but nothing is filler.

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 correctly carries the burden of describing the return payload, which it does thoroughly. For a read-only, zero-required-parameter tool the remaining gap is small: it never states the default behavior when `handle` is omitted or how large the response may be.

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 the baseline is 3, and the description earns above that by explaining the effect of `criteria` — it produces an evidence map rather than filtering the result, which the schema text ('Optional requirements to map against the portfolio') only hints at. It does not clarify the `handle` parameter, including what happens when it is omitted, which is the one semantic gap.

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 resource ('the candidate's complete structured portfolio') and enumerates its sections — experience, education, projects, writing, references, languages, awards — plus computed facts. 'Complete' signals it is the superset of narrower siblings like get_profile and get_project, though no sibling is named explicitly.

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 fetch-everything call, and the second sentence gives a clear condition for the optional `criteria` parameter. There is no explicit when-to-use/when-not guidance relative to get_profile, get_project, or match_criteria, which are the obvious alternatives.

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