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 covered. The description adds that each entry includes per-device sync state, which is useful context, but says nothing about result volume, pagination behavior, or error cases — with annotations carrying the safety burden, this is adequate rather than rich.

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 compact sentences: the payload scope first, the endpoint second. No filler, no repetition of the title, and the most important information leads.

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 tool with full schema coverage and no output schema, the description covers what the resource is, what it returns conceptually, and the endpoint. The only gap is the absence of any routing hint toward the inverse sibling tool, which keeps it short of a 5.

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 access_person_id, page, and per_page are all documented in the schema; baseline 3 applies. The description adds one small clarification — that the person may be an access user or a guest — but nothing about ID format or pagination semantics 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 (list) and a precise resource (doors, door groups, locations a single access user/guest can open), plus the underlying endpoint. The direction of the relationship (person -> devices) clearly separates it from the inverse sibling remotelock_list_device_accesses without needing to name it.

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 description implies the use case (finding what a specific person can open) but never states when to prefer it over remotelock_list_device_accesses, remotelock_get_access_person, or remotelock_list_group_items. No exclusions or prerequisites are given, so selection is left to inference.

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