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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is structured. The description adds concrete consequence beyond that: monitoring stops AND history is deleted, telling the agent what data is lost. It could go further on irreversibility or permissions, but it meaningfully extends the annotations.

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?

Two sentences, both front-loaded and load-bearing: the first names the action and its consequence, the second tells the agent where to get the ID. No 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 one-parameter destructive tool with no output schema and annotations covering safety/idempotency, the description supplies what an agent needs: the effect, the data loss, and ID provenance. Only minor gaps remain (e.g., whether removal can be undone or batched).

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 coverage is 100% and the endpoint_id property is already documented as coming from list_endpoints. The description restates that same provenance hint without adding new format or constraint detail, so it sits at the baseline for a fully documented single 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?

States a specific verb pair (stop monitoring, delete history) on a specific resource (one endpoint check). It is unambiguous against siblings like add_endpoint or recheck_site, which act on the same resource with different intents.

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?

"Use list_endpoints to find the endpoint_id" gives a clear prerequisite/routing hint to the sibling that supplies the required identifier. It stops short of explicit when-not-to-use guidance, but the intent is clear and there is no competing removal tool to disambiguate against.

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