Get group license quotas

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 the HTTP method (GET) and 'Body fields: none,' which is helpful, but it does not disclose pagination or response format. No contradiction with annotations.

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 compact and front-loads the purpose, then provides the endpoint scrape, body-field note, and documentation reference. Every sentence serves a purpose with no redundancy.

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 simple read-only GET with no required parameters and no output schema, the description plus schema gives enough to make the call correctly (endpoint and query behavior). A mention of the returned quota structure or any rate-limiting caveat would improve completeness, but it is not critical.

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 schema description for the single 'query' parameter is 100% covered (arrays comma-joined, explicit pagination, results not combined), so the schema carries the parameter documentation. The main description adds nothing about parameters beyond 'Body fields: none,' which is correctly stated.

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 states the specific verb ('Get') and resource ('group license quotas'), and includes the exact endpoint. This clearly distinguishes it from the sibling tool xmatters_get_user_license_quotas without ambiguity.

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 is provided on when to use this tool versus alternatives. The description does not mention that user license quotas are handled by a different tool, nor does it give conditions for selection.

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