emulator_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the qualifier that the emulator is 'official' and 'local', with no information on what status fields come back or whether the emulator must be running first.

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 nine-word phrase with the resource front-loaded and no filler sentences. It is efficient, though the word 'official' carries little usable meaning for an agent deciding whether to call it.

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?

With zero parameters and rich annotations, the basics are covered, but there is no output schema and the description says nothing about what a 'status' result contains (running state, version, endpoint, readiness). Combined with no distinction from emulator_health/emulator_doctor, an agent has to call it to learn what it does.

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 for the description to compensate for; the baseline for a no-parameter tool applies. Nothing in the description misleads about inputs.

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 names a specific verb ('Inspect') and resource ('local AWS Emulator status'), so the agent knows this is a read of emulator state rather than a mutation. However, it offers no differentiation from siblings like emulator_health or emulator_doctor, which sound like they inspect the same target, leaving the agent to guess which status-ish tool to pick.

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 when-to-use guidance and no mention of when NOT to use it or what to use instead. Given siblings named emulator_health, emulator_doctor, and emulator_self_test, the absence of routing guidance is a real gap rather than a minor omission.

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