Get lockkey

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description's one added piece of behavior is the return semantics ('none' if unlocked), which is genuinely useful since there is no output schema; it says nothing about auth requirements or what a nonzero lock owner string looks like.

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?

One short sentence with the resource path first and the return semantics second. Nothing superfluous and nothing buried.

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 single-parameter read tool with no output schema, explaining the sentinel value 'none' is the key contribution and it is present. But the sole parameter's meaning is left entirely undocumented, and nothing distinguishes this from the neighboring tuner status tools.

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% and the single required 'tuner' integer has no description anywhere. The '/tuner<n>/lockkey' path fragment vaguely implies the parameter selects a tuner index, but gives no valid range, indexing base, or whether it is required — the agent must guess.

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?

Names a specific resource (the per-tuner lockkey) and states the return meaning (current lock owner, 'none' if unlocked). The 'lockkey' term is distinctive enough to separate it from the many other hdhomerun_get_* siblings, though it never explicitly says it is the read counterpart of set_lockkey.

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?

No statement of when to call this versus alternatives, no mentioning of set_lockkey as the mutation counterpart, no preconditions. Usage is only inferable from the name and the word 'current'.

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