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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds meaningful context beyond that: the history is 'bounded' and the data are 'workflow/presentation signals, never scientific authority' — a useful trust/scope signal for downstream reasoning about the returned data.

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, no waste, and the scope statement (what is read) is front-loaded before the caveat about data authority. Every sentence earns its place.

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 input parameters, no output schema, and annotations covering the safety profile, the description needn't explain return values. It conveys the nature and trust level of the returned memory adequately; only the exact shape of 'routing history' is left implicit, which is acceptable given the absence of an output schema.

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 and the schema is empty, so there is nothing for the description to disambiguate. Baseline for a parameterless tool is 4; no syntax or scoping details are missing.

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 verb (read) and resource (the authenticated user's working preferences and bounded routing history), which is clearer than the bare tool name. It does not explicitly differentiate itself from the nearby sibling researchpilot_get_profile, so an agent must infer which of the two holds 'preferences' versus 'profile' data.

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: 'working preferences and bounded routing history' signals the retrieval context, and the note that these are never scientific authority hints at a supporting, non-primary role. No explicit when-to-use, when-not, or named alternative (e.g., get_profile or update_user_preferences) is given.

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