hosts_create

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds zero behavioral context: no required permissions, no uniqueness constraints on address/port, no statement of side effects, and no indication of what happens to the created host afterward.

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?

Four words, single sentence, no waste — but the brevity reflects under-specification rather than information density. Like the 'Process' calibration case, it is too terse to be useful, so it does not earn its place.

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 31-parameter mutation with nested objects, no output schema, and undocumented required fields, this description is completely inadequate. An agent cannot determine required inputs, parameter meaning, or how the new host relates to hosts_list/hosts_get from it.

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 has 31 parameters with only 3% schema description coverage and four required fields (inbound, remark, address, port), plus deeply nested mapper objects. The description mentions no parameters at all, so it fails to compensate for the near-total absence of schema documentation.

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 clear verb and resource ('Create a new host'), so the basic action is unambiguous. However, it adds nothing beyond the tool name: it does not define what a 'host' is in this API, give any scope, or distinguish the operation from siblings like hosts_clone or hosts_update.

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 when-to-use guidance, prerequisites, or alternatives are provided. The only signal is the trivial implication that you use it when you want a host created; siblings such as hosts_clone (copy an existing host) and hosts_update are never mentioned for routing.

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