delete_monitor

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

With no annotations, the description carries the full burden. The word "permanently" clearly communicates the destructive and irreversible nature of the operation, going beyond what the tool name alone conveys. However, it does not mention cascading effects or permissions.

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 concise sentence that delivers maximum information without waste. It is front-loaded and directly to the point.

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?

The tool has a simple structure with one parameter and an output schema. The description's mention of permanent deletion covers the essential behavioral context, and return values are handled by the output schema. Nothing important is missing.

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 fully documents monitor_id with a clear description. The description's "by ID" reinforces but does not add new meaning beyond the schema, so baseline 3 is appropriate.

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 "Permanently delete a monitor by ID" uses a specific verb (delete), resource (monitor), and method (by ID). It clearly distinguishes from sibling tools like reset_monitor or edit_monitor by emphasizing the permanent removal.

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 implies use for removing a monitor, but does not explicitly state when not to use it or provide alternatives. Sibling tools like reset_monitor suggest other actions, but no direct comparison is made.

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