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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: page size of 50, the nextCursor follow-up loop, and that `include` expands the parent project chain. It stops short of describing the monitor object or total/result-count behavior, which matters since no output schema exists.

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?

Three sentences, each earning its place: scope, pagination contract, optional expansion. The most important information (what is listed, and for what resource) is front-loaded with no filler.

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 read-only list tool with full schema coverage and annotations covering safety, the description supplies the missing pagination and expansion contract that the absent output schema would otherwise have to carry. Only the shape of an individual monitor record is left unstated, which is a minor gap.

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 100%, so cursor, include and project_id are already fully documented. The description's mention of `include` loading 'project, project.organization' restates the schema whitelist rather than adding meaning, so the baseline of 3 applies.

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 and resource ('List the monitors') scoped to a project, plus an ordering guarantee ('newest first'). This cleanly separates it from get-monitor-tool (single monitor) and list-monitor-analytics-tool (aggregate metrics), so an agent can select it without opening a schema.

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 implies when the tool applies (listing configured monitors for a known project) and gives pagination mechanics, but never names an alternative or states when NOT to use it, e.g. versus get-monitor-tool or list-monitor-analytics-tool. Usage is inferable rather than explicit.

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