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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds useful domain context (what a door group is and its role in one-step access granting) but says nothing about pagination behavior, result ordering, or what a caller receives — modest added value beyond the 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?

A single sentence plus the endpoint, with the core purpose front-loaded and the explanatory parenthetical earning its place by clarifying a non-obvious domain term. No filler.

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 list tool with full parameter documentation and clear safety annotations, the description covers the essential identity of the resource. It lacks any note on what a group record contains, but with no output schema that is a minor gap rather than a blocking one.

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%, and all three parameters (page, sort, per_page) are documented in the schema including defaults and the next_page chaining hint. The description adds no parameter-level meaning, so the baseline of 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 pairs a specific verb ('List') with a specific resource ('door groups') and even defines the domain concept via a parenthetical ('named sets of locks you can grant access to in one step'), which disambiguates it from siblings like list_group_items or list_devices. It stops short of explicitly naming a sibling it should be preferred over, keeping it at 4 rather than 5.

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?

Usage is only implied — an agent can infer you call this when you need door groups to grant access, but the description never states when to use it, when not to use it, or which sibling to pick (e.g., list_group_items vs list_door_groups). No explicit routing guidance is present.

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