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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuine context beyond them: it enumerates what is returned and discloses that a ready-to-read summary lives in a `say` field — valuable given no output schema exists. It stops short of stating auth-failure behavior or any rate limits.

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?

Three short sentences, front-loaded with the purpose before the payload contents and the `say` hint. Slightly weakened by the first sentence duplicating the title verbatim, which is minor wasted space.

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?

For a zero-param, read-only tool with rich annotations, the remaining burden is describing the return, and the description does list the aggregated fields and flags the `say` summary key. It is complete enough to call correctly, though the exact response shape is not fully enumerated.

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, so there is nothing for the schema or the description to disambiguate; the baseline for a parameterless tool applies. The description appropriately spends no words on absent inputs.

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 resource (the signed-in person's account) and enumerates its contents (saved jobs, applications, unread messages, interviews, Autopilot state, onboarding gaps), which differentiates it from single-purpose siblings like get_tracker, get_unread, or get_profile. It is clearly an aggregate/overview rather than a specific slice, though it never names a sibling 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?

The phrase 'at a glance' implies this is the dashboard/overview entry point, but the description never says when to choose it over get_profile, get_preferences, get_tracker, get_stats, or get_unread. Usage is implied rather than stated, which is the minimum viable level given the dense sibling set.

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