create_priority

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

Annotations already declare this is a non-read-only, non-destructive mutation. The description adds the 'admin' permission signal, which is useful context beyond the annotations. It still says nothing about behavior on duplicate keys, whether the created entity is returned, or what the operation's effects are.

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 front-loaded and has zero padding, but it is under-specified rather than concise: a single four-word sentence for a tool with four required parameters including a nested i18n object omits essentials the agent needs.

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 creation tool with four required params, a nested localization object, an admin permission requirement, and no output schema, the description leaves out required input format expectations (notably the i18n map for 'name') and any confirmation of what is returned.

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 75%, with the schema documenting key ('latin'), name (i18n map), and order ('display weight'), while 'description' is left undocumented in both schema and description. The description adds no parameter meaning whatsoever, 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 priority'), so the agent knows this is a priority-creation tool distinct from update_priority and get_priorities. However, it does not explicitly name those siblings or explain what distinguishes creation from them beyond the verb.

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?

The '(admin)' tag vaguely signals a privileged operation, but the description gives no when-to-use guidance, no prerequisites, and no alternative (e.g., update_priority for existing priorities). The agent must infer eligibility from the terse parenthetical.

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