sysknife_cloud_init_status

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the repeated 'read-only' phrasing adds no new information. The one piece of added value is naming the underlying command with `--long`, which hints at the depth of output returned. No disclosure of output format or failure modes beyond that.

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 compact line, front-loaded with the action name and the substantive purpose. Minor waste from saying 'Read-only' at the start and 'read-only' at the end, which is redundant with the annotations.

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 zero-parameter read tool with full annotation coverage and no output schema, the description supplies everything needed to invoke it, plus the concrete CLI command for context. Explaining the return shape would be a nice extra but is not essential here.

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?

Zero parameters, so the baseline is 4. The description correctly confirms 'no params', matching the empty schema, leaving nothing ambiguous for the caller.

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: show cloud-init provisioning status, with the concrete underlying command `cloud-init status --long`. No sibling covers cloud-init, so it is distinguishable, though it does not explicitly differentiate itself from the many other *_status tools in the family.

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?

Usage is only implied — an agent can infer to call it when it needs cloud-init provisioning state. There is no explicit when/when-not guidance or reference to an alternative (e.g., general host state via sysknife_get_host_state).

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