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

Annotations declare destructiveHint=true and idempotentHint=true, but the description says only "Save the display settings," adding no context about what is overwritten, whether partial updates are safe, or that workspace/repository scope is required. Nothing is contradicted, but the description contributes zero behavioral information beyond the annotations.

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 front-loaded sentence with no wasted words, but the brevity comes from under-specification rather than efficiency. There is no structure to distinguish the required scoping from the optional filter.

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 destructive, idempotent write tool with two required identifiers and an output schema, this is too thin: it omits the destructive semantics, the workspace/repository scope, and the status filter. The only thing it need not explain is the return value, since an output schema exists.

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 only 33%, so the description should compensate, yet it never mentions the two required identifiers (workspaceId, repositoryId) or the status filter enum. "Display settings" does not map to any of the three parameters, leaving required scoping undocumented in prose.

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?

"Save the display settings of the user" gives a verb (Save) and a resource (display settings), but "display settings" is vague and never clarifies what is actually persisted. It offers no differentiation from siblings such as read_preferences or settings.update, so an agent must guess which preference tool to pick.

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 prerequisites, and no mention of the read/write split implied by read_preferences. The agent is not told whether this overwrites or merges existing preferences.

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