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

Since `destructiveHint` is false, the description provides minimal additional behavioral context. It functions primarily to explain the purpose and usage flow rather than disclose complex behavioral traits like rate limits or state transitions beyond what the title suggests.

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 definition is highly efficient, using only two direct sentences. It prioritizes the function and immediately follows with workflow context.

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?

It is highly complete. By detailing how to find the required ID via sibling tools (`get_modules`), it satisfies the agent's immediate need to correctly structure the invocation.

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?

Even with 100% schema coverage, the description adds semantic value by clarifying the `site` parameter with examples of acceptable identifiers and providing a concrete use case for the optional `message` 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?

The description clearly identifies the specific action ('Mark an incident... as resolved') and the resource ('status incident'), leaving no doubt about its core function.

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?

It provides clear procedural guidance by directing the agent to 'get_modules' to list open incidents. This specifies the necessary preceding workflow step to acquire the required `incident_id`.

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