preference_summary

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

With no annotations, the description carries the full burden and does disclose one behavioral trait: it falls back to defaults when history is insufficient. It also specifies the output is human-readable and in Chinese. However, it does not state whether the tool is read-only, what 'transition' means, or any side effects, leaving moderate gaps given zero annotation support.

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 a single sentence that includes both the primary output and the fallback behavior without excess. It is slightly awkwardly phrased ('what you favour and how you transition') but remains efficient and front-loaded with the core purpose.

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-parameter tool with no output schema or annotations, the description provides sufficient context: what is returned (a sentence), in what language (Chinese), and a key edge-case behavior (fallback). It does not explain where preferences come from or define 'transition', but given the low complexity and sibling names, this is adequately complete.

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 has zero parameters, so parameter semantics are trivially complete. The description adds no parameter-related details because none exist, aligning with the baseline of 4 for no-parameter tools.

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 the tool produces a human-readable Chinese sentence summarizing user preferences and transitions, which is distinct from sibling tools that manage (learn/forget/import) preferences. It is specific about the resource and output language, though it lacks an explicit verb like 'generates' and does not name a sibling for contrast.

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 guidance on when to use this tool versus alternatives like learn_preferences or forget_preferences. The fallback note implies it is for display, but no conditions, exclusions, or alternative routing are provided. An agent would have to infer usage from the tool name.

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