Get your preferences

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

With no annotations, the description carries the full disclosure burden, and it adds little: it implies a read by defaulting to possession ("Your ..."), but never states whose preferences are returned, whether it errors when unset, or what the response shape is. Listing the preference categories is the only behavioral hint, and it is delivered as a bare noun list.

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?

It is a single short fragment with no wasted words, but it is under-specified rather than concise and is not front-loaded with an action. The enumeration of categories is the right content, just not framed as a complete statement.

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, annotation-free tool with no output schema, the listed categories do serve as a partial description of the return value, which is the main thing an agent needs. However, it omits the default/empty case and does not confirm that values are user-scoped, leaving a real gap given no output schema exists to define the response.

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, so there is no parameter semantics for the description to explain; the baseline for a no-parameter tool applies. The description does not need to compensate for any schema gap here.

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 is a noun phrase listing the preference categories ("humor styles, languages, categories, formats, caption tone and exclusions") rather than a verb+resource statement; the verb comes only from the title "Get your preferences." An agent can infer this returns stored preferences, but the description alone does not assert retrieval or distinguish it from set_preferences/get_compliance.

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 when-to-use guidance, no statement of prerequisites, and no mention of the obvious counterpart set_preferences or when a caller should read preferences versus another config-style tool. The agent must infer the calling context entirely.

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