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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only the HTTP route ('GET /groups'), and says nothing about pagination behavior, result volume, or ordering defaults that would deepen behavioral understanding.

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?

Three short sentences, front-loaded with purpose, then the filtering semantics, then the endpoint. There is essentially no padding; the trailing 'GET /groups' is only mildly redundant.

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 endpoint with full schema coverage and no output schema, the description covers what the resource is and how the two key filters work, which is adequate to call it correctly. Remaining gaps (sorting/paging behavior, result shape) are minor and largely handled by the schema.

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%, so all eight parameters (ids, sort, limit, query, scope, offset, lock_id, place_id) are already documented in the schema. The description's mention of filtering by place or lock is only a partial restatement of place_id/lock_id and adds no syntax or format detail beyond the schema.

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+resource ('List access groups') and even glosses the resource ('who-can-open-what bundles of doors'), which helps an agent understand the domain object. It does not explicitly contrast with the single-item sibling kisi_get_group or with kisi_list_group_locks, so it falls short of full sibling differentiation.

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 sentence 'Filter by place or by a lock to see which groups open that door' gives implied usage for the place_id and lock_id filters, but there is no guidance on when to prefer this tool over kisi_get_group, kisi_list_group_locks, or the other list endpoints, and no exclusions or prerequisites.

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