delete_matcher

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

No annotations are provided, so the description carries the full burden. It only says the tool deletes the matcher, but does not disclose whether deletion is permanent, requires special permissions, or impacts related data. For a destructive operation, this lack of behavioral context is a significant gap.

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, focused sentence that directly conveys the action and target. It is concise and front-loaded, with no unnecessary words.

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 delete tool, the description is minimal but does not address the permanence or side effects of deletion. With no annotations and no output schema, a more complete description should at least warn about the destructive nature or note that the action is irreversible.

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 defines a single integer 'id' with no description, and schema coverage is 0%. The phrase 'by ID' clarifies that the parameter identifies which matcher to delete, adding minimal meaning. However, it does not provide format constraints or additional context beyond the schema, so compensation is limited.

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 the specific verb 'Delete' with a clear resource ('integration matcher') and states deletion occurs by ID. This clearly distinguishes it from sibling tools like update_matcher and list_matchers.

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 its use for removing a matcher, but it does not explicitly state when to use it versus alternatives or mention any prerequisites or consequences. The resource is named, so the intent is clear, but no explicit usage guidance is provided.

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