create-downtime

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

No annotations provided, so description carries full burden. Only states 'create a downtime to mute monitors' but omits details on side effects, permissions, or behavior when overlapping downtimes exist. Lacks disclosure of what happens to notifications.

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?

Single sentence with no wasted words, but lacks structure (e.g., bullet points, sections). Acceptably concise but could be more scannable.

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?

Description fails to explain return values, parameter interactions (e.g., monitorId vs monitorTags precedence), or indefinite end behavior. With no output schema, this leaves the agent underinformed for a tool with 8 parameters.

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?

Schema coverage is 100%, so each parameter is described in the schema. The description adds no extra meaning beyond what the schema already provides, meeting baseline expectations without improvement.

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?

Clearly states the verb 'create', the resource 'downtime', and the purpose 'mute monitors by scope, monitor ID, or monitor tags'. Distinguishes from sibling tools like 'cancel-downtime' and 'list-downtimes'.

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 explicit guidance on when to use this tool vs alternatives like 'mute-monitor' or prerequisites. Does not mention required parameters or constraints, leaving the agent to infer from the schema.

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