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

Annotations already declare read-only, idempotent, non-destructive, so safety is covered. The description adds real behavioral depth: the meaning of monitor.state='failing', the ~30s re-check window, and the escalation to major_outage with team notification on the second consecutive failure.

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 return-field inventory, then drills into the state machine. Dense but every clause carries semantics; only minor redundancy in restating the failure-escalation rule twice.

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?

With no output schema, the description correctly carries the return-value burden: it explains lastFailure.message, ocorrenciaAberta, and the monitor.state semantics. An agent can interpret the response without a schema, though it does not cover fields it lists only by name (status, configuração).

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?

Single parameter with 100% schema description coverage, so the schema already explains that id is the 'id de listar_monitores'. The description adds nothing beyond the schema for the parameter, which is the expected baseline 3.

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 'Detalhe de um monitor' and enumerates exactly what is returned (status, configuração, último check, ocorrência). It is clearly a single-monitor detail read, distinguishable from listar_monitores, though it never names that sibling explicitly.

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 implied — fetch detail for one monitor by id — and it cross-references listar_ocorrencias for the occurrence object. There is no explicit when-to-use/when-not guidance or routing away from listar_monitores.

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