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

With no annotations, the description carries the burden of signaling behavior. It clearly indicates a read operation ('Returns') and describes the output contents, but it does not disclose ordering, time window, pagination behavior beyond the schema-provided limit, or any caveats about what 'recent' means.

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 a single focused sentence that front-loads the primary action and resource, then adds the key output detail. Every clause earns its place; there is no filler or redundancy.

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 simple two-parameter read tool, the description conveys the core purpose and output shape. However, it omits usage context relative to sibling tools and gives no indication of returned format, ordering, or any limits on history depth, so an agent has to infer some operational details.

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 only 50%: limit is documented, but monitorId is not. The description references 'a monitor' generically but does not explain how monitorId maps to a monitor or add any meaning beyond the schema. The description does not compensate for the undocumented required 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 uses a specific verb ('Returns') and resource ('recent check history for a monitor'), and adds detail about what that history includes ('detected changes with their relevance and explanation'). It clearly distinguishes itself from sibling tools like list_monitors and check_monitor, though it does not explicitly name them.

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 no guidance on when to use this tool versus alternatives such as check_monitor or capture_context. It implies a history/audit use case, but there is no explicit context, prerequisite, or exclusion to help an agent choose correctly.

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