emulator_start

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the mutation and safety profile is covered. The description adds one behavioral trait beyond the annotations (telemetry is disabled), but it does not disclose what happens on a repeat start despite idempotentHint=false, what port or endpoint is bound, or whether the call blocks until ready.

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?

A single short sentence with the action front-loaded and zero filler. The word 'official' is slightly promotional rather than informative, which keeps it just short of ideal.

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 start tool with annotations covering the safety profile and no output schema, the definition is close to sufficient. However, an agent still cannot tell whether the call is synchronous, what it returns (endpoint, readiness), or whether it should poll emulator_status/emulator_health afterwards — meaningful gaps for a launch operation.

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, so there is no parameter semantics to explain and the baseline of 4 applies. The empty schema with additionalProperties=false is fully consistent with a no-argument start command.

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?

States a specific verb and resource ('Start ... AWS Emulator'), which is unambiguous and implicitly the inverse of the emulator_stop sibling. It does not explicitly name or differentiate itself from siblings like emulator_status or emulator_health, but the action is clear from the verb.

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?

There is no guidance on when to use it versus alternatives, nor on preconditions such as whether the emulator must be stopped first or whether a status/health check should follow. The 'telemetry disabled' clause is a fixed configuration detail, not usage guidance.

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