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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the GET endpoint mapping, consistent with the read-only annotation, but says nothing about pagination behavior, result volume, or what the returned lock objects contain.

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 fragments with no filler, and the core resource statement is front-loaded. The trailing 'GET /group_locks?group_id=.' is a truncated endpoint snippet that contributes little, but the overall footprint is tight.

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 four-parameter read tool with full schema coverage and annotations covering safety, this is adequate but thin. With no output schema, the description could say what the returned locks include (name, place, door state) and confirm pagination, neither of which it addresses.

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 limit, query, offset, and group_id are all documented in the schema itself (including the pagination.next_offset hint on offset). The description only repeats group_id via the URL template, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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 resource and relationship: 'the locks/doors an access group opens', which is more informative than the bare tool name because it conveys the group-to-lock mapping. It does not, however, explicitly distinguish itself from the sibling kisi_list_locks (all locks) or explain how the two differ.

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?

There is no statement of when to use this tool versus kisi_list_locks, kisi_get_lock, or kisi_list_groups, and no exclusions or preconditions beyond the implicit required group_id. The REST endpoint string hints at the call shape but provides no selection guidance.

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