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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value beyond that: it clarifies cards are registered by Cluby and cannot be created here, explains the `secure` flag (NTAG 424 with a key, verified taps, can carry a stamp tag), and notes smartLinkId/Slug are null when loose. Useful behavioral and field semantics, though no pagination/volume info.

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?

Front-loads the resource, then enumerates the meaningful fields in a single organized sentence, closing with the list-vs-create boundary. Dense but every clause carries useful field context; 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?

With no output schema, the description appropriately explains the shape of returned cards (ids, secure flag, tapCount, attached smart link). Combined with the readOnly annotation, an agent has enough to call and interpret the result, though ordering/pagination details are absent.

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 the single optional orgId is fully documented in the schema. The description references publicId but that is a returned field, not an input parameter, so it adds no meaning to the actual orgId argument. Baseline 3 is appropriate.

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 the specific resource (the organization's physical NFC cards) and states the action explicitly at the end ('this lists and does not create them'). It also distinguishes itself from creation siblings (create_smart_link / update_smart_link), so an agent can tell what this tool does. The heavy focus on return fields rather than the action keeps it from 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?

Usage is only implied: by noting the 4-character publicId is what create_smart_link / update_smart_link take as smartCardPublicId, it hints this tool is the source for that value. There is no explicit statement of when to choose this tool vs alternatives or any prerequisites beyond that.

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