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

readOnlyHint=true already establishes the safety profile, and the description adds the underlying endpoint (GET /v1/organization/groups). However it says nothing about what comes back — no pagination behavior, no indication of whether the payload is a bare id/name list or richer group objects — which matters more here since there is no output schema.

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 clauses, purpose first, call-condition second, endpoint last — nothing redundant and nothing buried. Every element earns its place.

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 zero-param read-only list tool with readOnlyHint set and no output schema, the description covers what it does, why to call it, and the backing endpoint. The only meaningful omission is the shape of the returned group records, which an agent must discover at call time.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The omission of any parameter discussion is appropriate rather than a gap.

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?

Names a specific verb and resource ("List technician groups") that distinguishes it from sibling list tools such as gorelo_list_users or gorelo_list_clients. The parenthetical adds the reason the list matters (ids for ticket creation), though it doesn't state how groups differ in scope from users.

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?

"ids are needed to create a ticket" gives a concrete call condition that ties this tool to gorelo_create_ticket. It stops short of naming an explicit alternative or exclusion, but the practical when-to-use is clear.

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