update_status_page_incident

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

No annotations provided, so description carries full burden. It only says 'update' but doesn't clarify that null fields preserve current values, or mention side effects, permissions, or error states. The schema reveals more behavior than the description.

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 one sentence, concise but incomplete. It lacks important details about null-preserving behavior and additional fields, making it insufficiently informative despite its brevity.

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 the complex nested body object with multiple optional fields and null behavior, the description is too sparse. It doesn't explain the identifier requirements (page_id, incident_id) or the update semantics (null preserves current). An output schema exists but doesn't compensate for missing behavioral context.

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 mentions only three fields (title, impact, status), but the schema includes additional fields (affectedComponents, postmortemBody, postmortemUrl) with descriptions. The description adds minimal value beyond the schema's own parameter descriptions.

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 tool updates a status page incident and lists three fields (title, impact, status). It distinguishes from sibling tools like 'post_status_page_incident_update' which likely posts updates rather than modifying the incident directly.

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?

No guidance on when to use this tool vs. alternatives like 'dismiss_status_page_incident' or 'publish_status_page_incident'. No prerequisites or context provided for choosing this tool.

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