Get hostname

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

The description calls this a read operation and explicitly says read-only API keys are accepted, requiring services:read. This contradicts the annotations, which declare readOnlyHint=false and destructiveHint=true. The contradiction makes the behavioral signal misleading rather than transparent.

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 two compact sentences that front-load what is returned and then state the API-key/scope requirement. Every clause contributes useful information without unnecessary padding.

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 single-parameter read-style tool with no output schema, the description lists the returned hostname and management-mode information and states the required auth scope. It leaves some ambiguity around how to handle the listed fields and does not resolve the annotation conflict, but the call-relevant context is largely present.

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 single orderNo parameter is fully documented in the schema, including pattern and examples. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate given 100% schema description coverage.

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: get the current service hostname, reserved automatic hostname, and management mode. It implicitly distinguishes this read operation from sibling mutators like change_hostname and reset_hostname, but it does not explicitly name or route away from those alternatives.

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?

It gives useful invocation conditions such as accepting read-only API keys and requiring services:read with an API key. However, it does not say when to use this tool versus change_hostname, reset_hostname, or other service-information tools, so guidance is only partially covered.

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