Get AMP host status

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

The description discloses the tool returns state, uptime, and metrics, indicating a read-only operation. With no annotations provided, this is sufficient transparency for a simple get tool.

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, front-loaded sentence with no unnecessary words or repetition. Every part of the description adds value.

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 no-parameter tool returning host metrics, the description covers the key outputs (state, uptime, CPU, RAM). Absence of output schema is compensated by mentioning these fields. Minor gaps like response format or units do not detract significantly.

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?

No parameters exist, and schema coverage is 100%, so the description adds no parameter information. Baseline score of 4 applies due to zero parameters.

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 it retrieves state, uptime, and metrics for the AMP controller host machine. It distinguishes itself from sibling tools like amp_get_instance_status by explicitly saying 'not a game-server instance'.

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 implies usage for host-level information via the contrast with game-server instances, but does not provide explicit when-to-use or when-not-to-use guidance beyond that distinction.

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