Greenhouse MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete' implies a destructive mutation, but the description doesn't state whether this requires specific permissions, whether the deletion is permanent or reversible, what happens to associated data, or what the response looks like. For a destructive operation with zero annotation coverage, this is a significant gap in behavioral transparency.

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 maximally concise - a single sentence with no wasted words. It's front-loaded with the core action and resource. Every word earns its place, making it easy to parse quickly.

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?

Given this is a destructive mutation tool with no annotations, the description is minimally adequate but has clear gaps. The existence of an output schema helps (so return values are documented elsewhere), but the description doesn't address critical context like permissions needed, irreversible consequences, or relationship to sibling webhook tools. For a deletion operation, more behavioral context would be expected.

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 description doesn't mention any parameters, while the schema has 1 parameter with 0% description coverage. The baseline is 3 because the schema provides the parameter structure (rule_id as integer), but the description adds no semantic context about what rule_id represents, where to find it, or format requirements. This leaves the agent with incomplete understanding despite the simple schema.

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 the action ('Delete') and resource ('a webhook routing rule'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'webhook_update_rule' or 'delete_application' tools, which would require mentioning what specifically distinguishes webhook rule deletion from other deletion operations.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing an existing rule ID), when deletion is appropriate versus updating, or what happens after deletion. The sibling list includes 'webhook_update_rule' and 'webhook_list_rules' which are clearly related alternatives, but the description doesn't reference them.

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