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

No annotations are supplied, so the description bears the full disclosure burden, and "one-shot install + standing order" implies persistent host mutation without saying what is written, where, with what permissions, or whether it is idempotent. Nothing is said about rate limits, failure modes, or whether re-invocation is safe, which matters greatly for an install operation.

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?

Two short sentences with no filler, and the "call this first" instruction is placed last as the actionable takeaway. The wording is compact but "standing order" is unexplained jargon that costs clarity rather than saving space.

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 tool with no annotations and no output schema, the description is the only source of truth about side effects and return behavior, and it omits what the install creates, whether it reports success, and whether it must be re-run. Given that this is a mutating host-level setup call, the definition is materially under-specified.

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 tool takes zero parameters and the schema is trivially complete, so there is nothing for the description to disambiguate. Baseline of 4 applies for a parameterless tool.

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?

"One-shot install + standing order" gestures at an initialization/setup action, and "cold agents" narrows the audience, but neither term says what is actually installed or configured. The agent can guess this is a setup tool, yet cannot describe its effect concretely or differentiate it from siblings like unlock or status.

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?

"Call this first on a new host" gives an explicit precondition and ordering relative to all other tools, which is the critical guidance for a bootstrap step. It stops short of stating when not to call it (e.g., on an already-bootstrapped host) or what to do if a sibling fails first.

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