Unregister HTTP Target

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description enhances transparency by disclosing that the operation also removes stored check history, a behavioral detail not present in the annotations. This adds useful context without contradiction.

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 a single sentence 'Remove an HTTP target and its stored check history.' It is perfectly concise, front-loaded with the action verb, and contains no filler or redundant information.

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 simple one-parameter destructive operation with a clear annotation (destructiveHint=true) and no output schema, the description plus annotation covers the essential context. It could mention error behavior (e.g., if target not found) but this is not critical for a straightforward unregister action.

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 input schema has one parameter 'name' with no description (0% schema description coverage). The tool description does not mention the parameter or explain that 'name' identifies the HTTP target to remove, leaving the agent to infer this from context. Given the low coverage, the description should compensate but does not.

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 clearly states 'Remove an HTTP target' with the specific verb 'Remove' and resource 'HTTP target', and adds 'stored check history' to distinguish from other unregister tools. This precisely differentiates it from siblings like unregister_server or unregister_gitlab_pipeline.

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 context is clear: this tool is for unregistering HTTP targets. However, it does not explicitly mention when not to use it or suggest alternatives, relying on the resource name to guide the agent. No exclusions are stated, so this fits a 4.

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