apps_cli

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

With no annotations, the description carries the full behavioral burden. It does disclose the non-obvious requirement of a pre-existing login and implies the environment is non-interactive, which is useful. However, it does not state whether commands can create or modify resources, what output is returned, or how failures surface, leaving significant behavioral gaps.

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?

The description is two efficient sentences: it fronts the action, then gives examples, prerequisites, and cwd definition. There is no filler, and each clause 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?

No output schema exists, and the description never explains what the tool returns (stdout/stderr, exit codes) or how to interpret command failures. For a generic CLI runner with open-ended commands, this is a significant completeness gap; an agent cannot predict the result of 'submit' or 'playtest'.

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% for both parameters, so the schema already explains 'command' and 'cwd'. The description's example arguments ('init my-app', 'playtest', 'submit') merely echo the schema examples and add no new semantic information, keeping this at the baseline.

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 opens with a specific verb ('Run') and a specific resource ('official nodeloc-apps CLI command for in-site miniprograms'), and provides concrete examples ('init my-app', 'playtest', 'submit'). It is clearly distinct from all sibling tools, which cover forum, payment, and docs operations rather than executing a universal CLI.

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?

It states concrete prerequisites (CLI installed, logged in) and flags that interactive login must be performed manually in a terminal, which tells an agent when the tool is ready to use. It does not explicitly name an alternative because no sibling offers the same capability, but the usage context is clear.

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