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

Annotations already establish readOnly, idempotent, non-destructuctive behavior, and the description adds meaningful context beyond those: OAuth requirement, scoped API key support, $0.15 cost, API key requirement, opt-in location, and default inclusion of relationships and memories. No contradicion with annotations.

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 compact: three sentences covering purpose, configuraion, authentication, and costing. There is slight redundancy in the final sentence (OAuth + 'API key required' + '($0.15; API key required)'), but overall it remans efficient and front-loaded.

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 low-complexity, zero-required-parameter tool with a detailed input schema and an output schema, the description is complete. I covers authentication, cost, opt-in behavior, defaults for optional sections, and no hidden parameters exist. The output schema resolves the need to describe return values.

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 description coverage is 100%, and all three parameters already have clear descriptions and defaults. The description's 'pass include_*=false to omit' and 'Location is opt-in' largely restate the schema's defaults, adding little semantic value beyond what the input schema provides.

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 clearly states a specific action and resource: 'Get a snapshot of the authenticated user's current life context' with explicit component categories (identity, today/upcoming events, pulse, trackers). I does not explicitly compare against sibling tools like get_context_pack or get_events, so it misses the full 5-level 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?

The description implies use for obtaining a broad current-life snapshot and clearly explains configuration options (include_*=false, location opt-in), but it never states when to prefer this over alternatives or when not to use it. With many sibling tools such as get_context_pack and get_events, explicit usage guidance is absent.

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