preferences_get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds value by naming concrete preference keys (autoTextureReload, defaultTangentMethod, rayTraceBackend), but says nothing about behavior with unknown keys or the shape of the response (the output schema handles the latter).

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 compact sentence with the scope decision ('all or the given keys') front-loaded and concrete examples appended. No filler, though it is a fragment rather than a complete statement of action.

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 an output schema and full annotations, the description doesn't need to explain return values or safety. It is adequate for a simple getter, but omits what happens with invalid/unrecognized keys and never references preferences_set, leaving a small gap an agent would want covered.

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 description must carry the load for the single 'keys' parameter — and it does: it explains that omitting keys returns all preferences and supplies three real key names as examples. Only the exact key format/casing rules remain unspecified.

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 names the resource (Toolbag application preferences) and clarifies the scope — either all preferences or only the supplied keys — which lets an agent distinguish it from the sibling preferences_set. It reads as a noun phrase rather than an explicit verb, but combined with the name the retrieval purpose is unambiguous.

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 and no mention of preferences_set as the write-side alternative. The only usage hint is implicit in 'all or the given keys' (omit keys to get everything), which is really parameter behavior rather than routing guidance.

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