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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds value beyond them by disclosing the required read scope and describing the repo-monitor relationships (parent_monitor_id, repo, split_by_repo). It omits pagination/result-size behavior for a potentially unbounded list, keeping it from a 5.

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 auth scope and core behavior are front-loaded correctly. The final sentence about repository monitors is long and tangential for a list tool, packing parent_monitor_id, repo, split_by_repo and LastPing's creation model into one dense clause that strains focus.

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 usefully enumerates the return fields, and it covers auth scope and the one supported filter. It leaves out ordering, pagination or result limits, which matter for a list-all tool, so it is strong but not fully complete.

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%, so the tag parameter is already documented with an example in the schema. The description adds the constraint that only a single tag is accepted ('monitors carrying one tag'), a marginal but real clarification, so the baseline 3 is appropriate.

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 ('Lists every monitor in the project') and even enumerates the returned fields (id, name, slug, status, ping_url), so the agent knows exactly what comes back. The 'every monitor' phrasing implicitly contrasts with the singular get_monitor sibling, but that differentiation is not stated 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?

Provides a prerequisite ('Requires the read scope or higher') and states that tag narrows the result set, which is useful context. However, it never says when to reach for this vs get_monitor or list_discovered_agents, nor any when-not condition, so usage is only implied.

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