sysknife_get_apt_pins

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the two 'read-only' mentions in the description are pure repetition. The one piece of added value is disclosing the apt-cache policy backing, which hints at the shape of the output. It says nothing about whether elevated privileges are needed or how a missing package argument behaves.

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?

Very short and front-loaded with the verb and resource. The trailing 'read-only' duplicate and the quoted internal action name add minor noise but nothing substantial.

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-only inspection tool with annotations covering safety and no output schema, the description is nearly sufficient: it names the resource and the underlying command. It falls short only on argument behavior and privilege requirements.

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?

The schema declares no properties (additionalProperties: true), so the description's note that 'package' is an optional argument is genuine added value. However, it gives no format or matching semantics for that argument, nor does it say what is returned when the argument is omitted (presumably all pins).

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 concrete action (show apt pin priorities) and even names the underlying mechanism (apt-cache policy), which tells an agent exactly what data comes back. It is distinguishable from siblings like sysknife_apt_show or sysknife_apt_list_installed, though the differentiation is implicit rather than stated.

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 guidance on when to choose this over sysknife_apt_show, sysknife_apt_list_upgradable, or other apt siblings, and no mention of when pin data is relevant (e.g. debugging held-back upgrades). The only qualifier is 'read-only', which is not usage guidance.

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