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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful value beyond that by disclosing the return data shape (status, assignee, last use) in the absence of an output schema, plus the underlying endpoint. It still omits pagination/rate-limit behavior, which the schema only partially hints at.

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 with the resource and returned fields front-loaded; nothing is padded. The trailing "GET /cards" is marginal filler for an MCP agent but harmless and cheap.

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 6-parameter, all-optional list tool with full schema coverage and annotations covering safety, the description supplies the one thing structured data lacks — the fields returned by each card. Pagination semantics live in the schema (pagination.next_offset referenced in offset), so little is missing.

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 the schema already documents ids, sort, limit, offset, status, and user_id thoroughly. The description only echoes the status enum values, adding no syntax or behavioral detail beyond the schema — 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?

States a specific verb ("List") and resource ("access cards") and even enumerates the returned attributes (status, assignee, last use), so the agent knows exactly what it gets back. It does not explicitly differentiate itself from siblings, but "cards" is a distinct resource from locks, users, groups, etc., so disambiguation is easy.

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 or when-not-to-use guidance, no mention of prerequisites or alternatives, and no statement about filtering behavior beyond what the schema already lists. The listing intent is only implied by the verb.

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