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

With only readOnlyHint=true in the annotations, the description carries the return-shape burden (there is no output schema) and does so well, spelling out the webhook `{ endpointId, ref }` versus null distinction and the `smart_link.scanned` event emitted on venue-target scans. Much of the remaining prose (409 on double-attached cards, detaching via update_smart_link) describes sibling mutations rather than this read, which is genuinely useful domain context but slightly off-target.

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?

For a one-parameter read, the description is heavily bloated: most of it narrates action/target encodings, webhook tying, card attachment and a 409 detach workflow that belong to create_smart_link / update_smart_link. The purpose is front-loaded, but the excess text risks leading an agent to expect mutation behavior from a read-only tool.

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 compensates by documenting every returned field, the action/target grammar, and webhook nullability, plus org scoping via orgId. An agent can interpret the response without further lookup; only the return-container/pagination shape is unaddressed.

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?

A single parameter with 100% schema description coverage, so the schema already explains that orgId is the `id` from list_orgs and may be omitted for single-org keys. The description adds nothing param-specific, which is the expected baseline when the schema does the work.

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 opening clause names the resource precisely — smart links (QR / NFC tag targets) of an organization — and enumerates the fields returned (url, action, target, card/visit counts, webhook), so an agent knows what it gets. It never states the verb 'list' outright and never contrasts itself with create_smart_link / update_smart_link, but the resource is unambiguous.

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 when-to-use guidance: nothing says 'call this to enumerate an org's tag targets' or when to prefer it over list_nfc_cards / list_webhook_endpoints. Other tools are named only as dependency lookups (list_webhook_endpoints, get_pos_connection), not as alternatives this tool replaces or complements.

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