create_resolution

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. The description adds one piece of behavioral context beyond that: it is an admin-scoped operation, implying elevated permissions. It says nothing about idempotency, uniqueness of the key, or what happens on duplicate input, so it is adequate but thin.

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 short sentence with the action front-loaded and zero filler, but it is arguably under-specified rather than concise. The '(admin)' fragment is efficient signalling, yet there is not enough content for a higher structure score.

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?

This is a mutation tool with no output schema and a nested localization object, yet the description does not say what is returned, whether the key must be unique, or how the created resolution is used. Given the complexity of the input and the absence of annotations covering these points, the description leaves meaningful gaps.

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 description coverage is 100%, with the key format ('Latin key starting with a lowercase letter') and the name localization object shape documented in the schema itself. The description adds no parameter meaning, so the baseline 3 applies.

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 and resource ('Create a resolution'), which an agent can distinguish from get_resolutions and update_resolution by verb alone. The '(admin)' qualifier adds a scope hint. It does not, however, explain what a resolution is or how it relates to the sibling resolution tools, so it stops short of a 5.

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 and no mention of alternatives such as update_resolution or get_resolutions. The parenthetical '(admin)' is the only contextual cue, implying a permission prerequisite but not a usage condition.

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