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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the organization-wide scope and confirms filtering/pagination behavior, but says nothing about result ordering or default page size beyond what the schema states.

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?

Two short sentences with the scope stated first and the filtering options second; no filler. Slightly terse for a list endpoint but well front-loaded.

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 no output schema, an agent still lacks information about what an incident object contains and how results are ordered or paginated by default. The description covers invocation basics but leaves return-shape expectations implicit.

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 75%, with status enum, limit default/max and monitorId already documented in the schema. The description only restates the filterable fields (status values, monitor id, pagination) without adding syntax or edge-case meaning, so baseline 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 incidents) and scopes it to the authenticated organization, which distinguishes it from vs_incidents_get by id. It does not explicitly contrast with sibling list tools, but the resource is unambiguous.

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 phrase 'Filter by status..., monitor id, or paginate' implies how to narrow results, giving implied usage guidance. However, it never says when to use this list versus vs_incidents_get for a single incident, or how it relates to vs_incidents_update / vs_incidents_mark_resolved.

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