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 readers report model and online/offline status and that it maps to GET /readers, which is useful but modest; nothing is said about pagination limits or result size.

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 sentences, front-loaded with the resource identity and details. Every clause carries information and nothing is padded.

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?

With no output schema, the description partially compensates by naming returned attributes (model, status), and the tool is a simple filtered list whose parameters are fully documented in the schema. Missing pagination behavior detail (offset/limit semantics are only in the schema) keeps it from 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 all six parameters (limit, query, offset, status, lock_id, place_id) are already documented with constraints and one enum. The description adds only an indirect nod to status via "online/offline status" and supplies no syntax or filtering guidance 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?

Names the resource precisely (readers) and even explains what a reader is ("card/phone readers at doors"), plus the fields returned (model, online/offline status) and the backing endpoint GET /readers. It does not differentiate from sibling list tools such as kisi_list_locks or kisi_list_controllers, so it falls short of a 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?

There is no statement of when to use this tool versus alternatives, no prerequisite context, and no exclusions. The filters exist in the schema but the description never hints at scoping by lock, place, or status, so the caller gets no routing guidance.

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