Get integrations

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'Body fields: none' and the endpoint, but no details on pagination or response behavior. The schema's query description partially fills that gap.

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?

Four short sentences with no fluff: verb, endpoint, body note, and reference. The information is front-loaded and relevant, though slightly terse.

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 two parameters, no output schema, and a collection-resource tool, the description is too sparse. It does not clarify what integrations are returned, how to filter, or when to use this list endpoint vs the singular variant, leaving the agent to infer from the schema and sibling names.

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?

The description adds no meaning about planId or query parameters beyond restating the endpoint and body fields. Schema description coverage is only 50%, yet the description does not compensate by explaining what planId represents or how the documented query parameters (integrationType, deployed, embed) behave.

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 'Get integrations' and the exact endpoint, which clearly conveys it lists integrations for a plan. The plural endpoint and sibling xmatters_get_an_integration distinguish it from fetching a single integration, though it does not explicitly say 'list all'.

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?

No guidance on when to use this tool versus alternatives like xmatters_get_an_integration or xmatters_get_integration_logs. The reference link is not usage guidance, and there is no mention of when the query filters should be used.

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