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

Adds useful context beyond annotations: it mentions the read scope requirement, the exact fields returned (assertions, guards, routes), their semantics, and the fact that they are absent when empty. It also notes how update_monitor and set_route interact with these sets, which helps understand read-before-write patterns. Annotations already cover read-only, idempotent, non-destructive, so the bar is lower, and this adds meaningful detail.

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?

Front-loaded with the core action and scope requirement. The description is dense but information-rich, with no obvious filler. Slightly longer than necessary but each sentence contributes useful context.

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 a simple read tool with one parameter, full schema coverage, and annotations covering safety, the description is nearly complete. It explains the returned fields and their relevance to update operations. It does not describe output format (no output schema), but for this read tool that is a minor gap, hence not a 5.

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 coverage is 100% and the single parameter id is fully documented in the schema as 'Monitor UUID.' The description does not elaborate on the id parameter beyond what the schema provides, so baseline 3 is correct.

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+resource: 'Gets one monitor by UUID with its full configuration.' This distinguishes it from list_monitors, create_monitor, update_monitor, etc. However, it does not explicitly name sibling alternatives for comparison, so it falls short of a 5.

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?

Clearly implied when to use: when you need a monitor's current configuration by UUID. It also implicitly contrasts with update_monitor and set_route by noting that those replace whole sets while this returns current sets, which helps an agent decide whether to read first. No explicit exclusions or prerequisites beyond scope requirement.

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