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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description doesn't need to restate these. The description adds context about auth requirements ('Requires a free watch key or paid API key') and what the report includes, but it doesn't disclose what happens if no monitors exist, whether the report is generated on-demand and returned or queued, or any rate limits. It doesn't contradict annotations.

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?

Three sentences, all useful and no wasted words. The main action and scope are front-loaded, the inclusion list is concise, and the auth requirement is appended as a final note. Could perhaps integrate the auth note earlier, but it is not misleading 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?

The tool has an output schema, so the description need not explain return values. The description covers purpose, scope, and auth requirements. Given the tool is a read-only report generator with clear params and an output schema, the only missing context is subtle: what the report format is (though output schema covers it) and what happens in edge cases like no monitor activity. But overall it's adequate for an agent to select and invoke it correctly.

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 schema already documents both parameters. The description mentions 'time window' but doesn't explicitly map it to the 'period' parameter beyond what the schema says. The description doesn't add details like whether include_unchanged only affects the report's visibility or also affects processing. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 states a specific verb ('Generate') and resource ('summary report of monitor activity'), clearly distinguishing it from sibling tools like list_monitors or get_monitor_result. The title reinforces the action. The scope of the output (monitors run, changes detected, failures, risk levels, recommended follow-up actions) also clarifies what this report contains, and it is distinct from other tools like assess_compliance_posture or test_hypothesis.

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 gives clear context regarding when to use this tool: when a summary report of monitor activity is desired, with a specific time window. It implies the difference between this and get_monitor_result or list_monitors by focusing on an aggregated report rather than a single result or simple list, but it does not explicitly exclude alternatives or state conditions like 'use this instead of list_monitors when you need an aggregated summary.'

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