createApp

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

With no annotations, the description is fully responsible for disclosing behavioral traits, but it only repeats the tool's name. There is no mention of side effects, required permissions, asynchronous behavior, or what happens upon creation, leaving agents to guess at the tool's consequences.

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 very short but this is under-specification rather than effective conciseness. It restates the tool name without adding value, so the sentence does not earn 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?

The tool has three required parameters and no additional context from schema or annotations. The description is wholly inadequate to understand the tool's purpose beyond trivial creation, leaving major gaps about input requirements, return values, and operational effects.

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 has 0% description coverage for its three required parameters, and the description does not mention any of them. It fails to compensate for the lack of schema documentation, providing no insight into what app_handle, account_handle, or docker_image mean or how they should be supplied.

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 states a clear verb and resource: 'Create a new app.' This distinguishes it from other app-related operations like getApp, configureApp, and deleteApp, though it doesn't explicitly differentiate from sibling creation tools like createAccount. The intent is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites such as needing an existing account or stack. The single sentence offers no context for usage decisions.

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