start_app

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without mentioning side effects, required permissions, idempotency, or error conditions. For a mutation tool, this is insufficient; the agent has no insight into what happens during startup.

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 a single sentence, making it concise. However, it is too brief to be adequately informative. It is not wasteful, but it sacrifices completeness for brevity. The length is appropriate only if the tool is trivial, but given the lack of other documentation, it is insufficient.

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?

Given the low schema coverage, absent annotations, and the fact that this is a mutation tool, the description is incomplete. It does not reference the output schema or relate to sibling tools like stop_app. The agent lacks essential context to use the tool correctly within the app management flow.

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 input schema has 0% description coverage, and the tool description adds no meaning to the 'app_name' parameter. It does not explain what identifies an app, expected format, or examples. The agent must rely on the parameter name alone, which is insufficient for correct invocation.

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 clearly states the action 'Start a stopped app.' It uses a specific verb and resource, distinguishing it from siblings like stop_app or install_app. However, it is terse and could elaborate on what 'start' entails, but the purpose is unmistakable.

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?

The description provides no guidance on when to use this tool versus alternatives like install_app or stop_app. There are no prerequisites, exclusions, or context about when it is appropriate to start an app. The agent must infer usage from the tool name alone.

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