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

Annotations already mark this as read-only and non-open-world, so the safety profile is covered. The description adds useful behavioral context: the tool returns a per-monitor breakdown and is designed for batched multi-monitor queries rather than per-monitor loops.

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?

Two concise sentences. The core purpose is front-loaded, and the batching instruction follows without redundancy or filler.

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 read-only trend query with no required parameters and a rich schema, the description is nearly sufficient. It doesn't detail the exact return shape beyond 'per-monitor breakdown,' but given the simple tool type and strong schema, that is a minor gap.

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 description coverage is 100%, so the baseline is 3. The description mentions monitor_uuids batching, but the input schema already documents that behavior in more detail, so the description adds little beyond the 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?

States a specific verb and resource: 'Response time latency trend over a date window.' It also clarifies the output shape ('Returns a per-monitor breakdown'), which distinguishes it from sibling metric tools like get_monitor_uptime or get_monitor_mttr.

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?

Provides clear invocation guidance: pass all monitors at once in monitor_uuids rather than calling once per monitor. It doesn't explicitly name alternative tools or say when not to use it, but the date-window and response-time context makes the intended use clear.

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