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

The annotations already mark this as read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond that: it is for the authenticated user, requires an API key, costs $0.20, and specifies which sections are included by default or remain opt-in. This gives the agent a clear picture of side effects, auth needs, and cost.

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 dense sentences carry the core purpose, tunable flags, sensitive-section opt-ins, spec link, cost, and auth requirement. Every sentence earns its place and the most important content is 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?

Given the output schema exists and all parameters are optional and well-described in the input schema, the description covers the key invocation concerns: cost, authentication, default sections, and opt-in behavior. The main completeness gap is the lack of differentiation from get_life_context, which could matter in tool selection.

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 baseline is 3; the schema already documents all eight parameters. The description reinforces the semantics of include_relationships, include_memories, location, and money, but does not add meaningful detail about focus, query, include_trips, or include_places. It neither hurts nor significantly improves on the schema.

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 identifies the resource as a Life Context Protocol pack for the authenticated user and lists its sections: identity, pulse, who_matters, whats_next, memories. However, it does not explicitly distinguish itself from the closely named sibling get_life_context, so a bit of differentiation is missing.

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?

It gives useful usage direction: pass include_relationships/include_memories false to omit sections, and location/money are opt-in. It also notes the API key requirement and cost. But it never says when to choose this over sibling tools like get_life_context or notable_pack, leaving the selection logic implicit.

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