get_preset

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it returns a single exact record rather than a list, which is useful, but it does not describe error behavior, return format, or what a 'catalog record' contains. Since annotations handle the main safety disclosure, a mid-level score is appropriate.

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, tightly worded sentence that front-loads the action and object. No filler or redundant information. Every word earns its place.

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 simple read operation with one well-documented parameter and annotations covering safety, the description gives enough to invoke the tool correctly. It lacks explicit information about not-found behavior or return payload structure, but the term 'NKS preset catalog record' is fairly self-explanatory in domain context. Completeness is good for the tool's simplicity.

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%: presetId is already described as 'Stable NKS preset catalog ID.' The description does not add further semantic detail about the parameter, so the schema carries the full burden. 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?

The description states a specific verb ('Read') and a precise resource ('one exact NKS preset catalog record'). This clearly distinguishes it from siblings like search_presets (search vs. exact lookup) and get_preset_metadata (full record vs. metadata). No ambiguity about what the tool does.

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 word 'exact' communicates that this tool is for fetching a single record by its stable ID, implying it should be used when the caller already knows the exact presetId. However, it does not explicitly name alternatives like search_presets or mention when not to use it, so it falls short of full alternative routing.

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