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

The readOnlyHint annotation is consistent with the description, and the description adds useful behavioral detail: it clarifies that the tool returns per-check pass/fail status and drift details, and that empty results are possible when schema validation is off. No destructive side effects are implied or hidden.

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 only two sentences and front-loads the core purpose. It packs the output contents, return condition, and prerequisite into a compact form without redundant phrasing or unnecessary detail.

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 lack of an output schema, the description compensates by summarizing the return shape (per-check status and drift item fields) and by stating the key precondition (schema validation must be enabled). It could mention the relationship to check_schema_drift more explicitly, but it is sufficiently complete for correct invocation.

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 schema already covers all parameters with clear descriptions, including monitorId's source ('from list_monitors') and the meaning of to/from/take. The description adds little beyond the schema, so it meets the baseline but does not elevate parameter understanding further.

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 opens with a specific verb and resource: 'Get what a monitor's schema validation found', and then enumerates the exact output components (per-check pass status, drift items, JSON path, severity, expected/actual value). This makes the tool's purpose unmistakable and distinct from generic report or monitor list tools.

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?

It provides some usage context by noting that results are only returned when schema validation is enabled and that project context is required, and it points to manage_drift_watch for enabling the feature. However, it does not explicitly contrast with the sibling check_schema_drift or list_monitor_checks, so an agent might need to infer when this report tool should be preferred.

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