Get bounded personalization context

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds real context by saying the read is 'minimum' (bounded/least-privilege) and spans four specific domains, but it says nothing about permissions, latency, or how the returned slice varies by task.

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?

A single tightly-worded sentence with no filler, and the scoping qualifier ('minimum') is front-loaded. It is efficient, though it is arguably too terse given the unexplained enum and absent output contract.

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?

There is no output schema, so the description carries the burden of describing what comes back — and it does not, beyond naming four domains. Combined with an entirely undocumented task enum, an agent cannot know what it will actually receive or which task value fits its situation.

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 0%, so the enum values are listed but never explained. The description partially compensates by implying the returned context is task-conditional ('minimum ... needed for one supported task'), which tells the agent that different enum values yield different context slices, but it does not define what 'recommendation', 'voice', 'pantry', or 'portion' actually return.

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 gives a specific verb ('read') and a compound resource ('safety, profile, memory, and pantry context'), which conveys that this is an aggregating context fetch rather than a single-domain getter. However, 'one supported task' is never disambiguated and the tool is not distinguished from siblings like get_profile, list_safety_constraints, or list_memories, which retrieve the same underlying domains.

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?

There is no explicit when-to-use guidance, no statement of when to prefer this bundle over calling get_profile/list_memories/list_safety_constraints directly, and no prerequisites. 'Needed for one supported task' hints at a workflow but never names the conditions that select this tool.

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