Get scenarios

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds the GET method and 'Body fields: none', but does not disclose additional behavioral details such as response shape, pagination behavior beyond what the schema already says, or any API-specific caveats.

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 description is short and front-loaded, with the endpoint, body requirement, and reference link each adding useful information. It loses a point because 'Get scenarios' largely restates the tool name/title rather than adding new substance.

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?

The schema and annotations cover invocation safety and query parameters well, and the reference link is useful. However, the description does not state what the response contains and does not distinguish this plural list operation from closely related sibling tools, so an agent may still be uncertain about scope.

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% and the query parameter description is informative, covering documented names, comma-joining of arrays, and explicit pagination. The main description adds no parameter-level meaning, so the baseline of 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?

The description names a specific verb and resource ('Get scenarios') and provides the exact endpoint, so an agent can tell this is a collection-level GET. However, it does not explicitly differentiate itself from siblings like xmatters_get_a_scenario or xmatters_get_scenarios_in_a_form, leaving some ambiguity about scope.

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 gives no guidance on when to choose this tool over alternatives. It does not mention that this is the plural/list variant versus singular or form-scoped variants, and it does not state any conditions or exclusions.

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