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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. Beyond that, the description adds genuine value by disclosing the returned record types and that each run carries a reason, which partially substitutes for the absent output schema. It says nothing about ordering, pagination behavior, or how far back history extends.

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?

A single tight sentence with no filler, front-loading the read action and the result categories. It is efficient, though brevity here comes partly at the cost of the parameter explanation the schema lacks.

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 three-parameter read tool with no output schema, the description covers what comes back (run statuses plus reasons) but leaves the pagination contract undefined. An agent can call it with only schedule_id, yet cannot use before/limit correctly without trial and error.

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 0%, so the description must carry parameter meaning and it does not. Only schedule_id is obliquely implied by "a monitor's"; limit and especially before (an opaque string that reads like a pagination cursor) are given no semantics at all. An agent must guess the format and direction of the cursor.

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 pairs a specific verb ("Reads") with a specific resource (a monitor's runs) and enumerates the run outcomes returned (completed, blocked, missed). This clearly separates it from list_capacity_schedules, which lists the monitors themselves rather than their runs. It stops short of naming that sibling explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied: an agent can infer this is the tool for inspecting a single monitor's run history, including failures. There is no explicit statement of when to prefer it over list_capacity_schedules or get_capacity_schedule, and no mention of prerequisites such as needing a known schedule_id.

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