Stop metrics collection

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

Annotations already indicate this is a mutating, non-idempotent, non-destructive action. The description adds useful behavioral context beyond that by explicitly mentioning SSH session cleanup as a side effect. It does not disclose all potential failure modes or prerequisites, but it gives a meaningful behavioral profile.

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 generally front-loaded, but the first sentence simply restates the title, while the second sentence carries the real content. This redundancy keeps it from being maximally efficient, even though there is no extraneous 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?

For a state-changing tool with two parameters and no output schema, the description should explain the meaning of the parameters, the preconditions for stopping collection, and likely results. It only states the high-level action and SSH cleanup, leaving important operational details unspecified.

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?

Schema description coverage is 0%, so the description must compensate, but it does not explain what 'id' refers to, what viewerSessionId is for, or how the parameters relate to the host. The vague phrase 'for a specific host' hints at id's role but is insufficient for an agent to confidently populate the required parameter.

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 uses a clear verb ('stops') with a specific resource ('metrics collection for a specific host') and adds the distinct side effect of cleaning up the SSH session. It is distinguishable from the inverse sibling start_metrics_collection, though it does not explicitly name any alternative.

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 clearly conveys this tool is for stopping an ongoing collection and cleaning up the SSH session, which gives the agent immediate context on when to call it. It does not mention exclusions or name alternatives, but the intended use case is evident from the stated behavior.

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