webapp_start

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

No annotations provided. The description does not disclose side effects, safety profile, or whether starting is a read-only or mutating operation. It does not mention if it requires special permissions or triggers any background processes.

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 (two lines) and not verbose, but it is underspecified for a tool with two required parameters and no annotations. While every sentence earns its place, the description is too minimal to be fully helpful.

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 existence of an output schema (but not shown), the description does not explain return values or postconditions. For a simple start action, it might suffice, but it lacks context about prerequisites (e.g., web app must exist) and behavior (e.g., what happens if already running).

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 0%, so the description must add meaning beyond parameter names. It only lists 'name' and 'resource_group' without any format, constraints, or context. For example, it does not clarify that 'name' is the app name and 'resource_group' is the group containing the app, which is already implicit.

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 explicitly states 'Start a web app,' which is a clear verb+resource. The tool name and sibling tools (webapp_stop, webapp_restart) clarify that it starts a stopped or existing app, but the description does not mention prerequisites or distinguish from creation.

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 on when to use this tool versus alternatives like webapp_create_for_container or webapp_restart. The description lacks context about required prior actions (e.g., the web app must already exist and be stopped).

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