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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real context beyond them: the newest-first sort order, the exact field set returned, and the OAuth scope (decks:read) required to call it.

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 tightly written sentences with zero filler; the scope and returned fields come first and the auth requirement second. Every clause carries information.

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 correctly compensates by listing the returned fields and the sort order, and it discloses the auth requirement. The only material gap is pagination behavior for limit/offset, which matters for a list tool bounded at 50 items.

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 only 50%: offset documents 'From the previous answer's next_offset' but limit has no description at all, only min/max bounds. The description says nothing about page size, defaults, or pagination, so an agent gets no guidance on the one parameter the schema leaves undocumented.

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 a specific resource (the signed-in user's ArcaneMetriX decks) and enumerates the returned fields: name, format, commanders, card count and bracket, plus the newest-first ordering. That is enough to separate it from single-deck siblings like get_my_deck, though the description never names that alternative explicitly.

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?

The prerequisite 'Needs the user to connect their account (decks:read)' is a genuinely useful usage condition. However, there is no explicit statement of when to prefer this over get_my_deck or analyze_my_deck; the browsing use case is only implied by 'my decks'.

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