Start metrics collection

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

Annotations already establish that this is not read-only and not idempotent, and the description adds meaningful context by revealing that an SSH connection is established and host-specific metric collection begins. However, it does not disclose what happens on repeated calls, whether collection persists, or how it is later stopped.

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 short and front-loaded, with the second sentence adding useful SSH and host-scope details. The first sentence echoes the title, but the overall structure is efficient and free of unnecessary filler.

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 no output schema and only one parameter, the description provides the basic action but is incomplete for correct invocation. It does not clarify the semantic of the id parameter, mention host prerequisites or reachability, or describe the expected result of starting collection.

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 schema has one id parameter with 0% description coverage, and the description only refers to 'a specific host' without explicitly connecting id to a host identifier or explaining how to obtain it. This gives minimal semantic value beyond the raw integer schema and leaves room for ambiguity among host-related IDs.

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: start metrics collection for a specific host, and adds the useful detail that an SSH connection is established. It is not a bare tautology, but it does not explicitly distinguish itself from sibling collection/polling tools such as start_polling_updated_host or stop_metrics_collection.

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 guidance is given about when to use this tool versus the many metrics siblings, such as stop_metrics_collection, start_polling_updated_host, or refresh_polling. There are also no prerequisites, exclusions, or alternative routing details, so the agent must infer usage from the name and basic description.

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