conflict_eligible_cards

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

No annotations are provided, so the description carries the full burden, and it delivers: it explains sampling semantics, warns not to equate returned UID count with all eligible cards, clarifies that qty/total_cards retain full counts, discloses no continuation-page fetching, and states row/KiB truncation limits. This is unusually rich and actionable behavioral disclosure.

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?

The purpose is front-loaded and nearly every sentence adds behavioral value, so the length is justified. Minor grammar and punctuation issues, such as 'Makes one logical GET request Does not auto-fetch continuation pages', reduce polish without obscuring meaning.

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 read tool with no annotations and no output schema, the description covers purpose, parameter semantics, response-interpretation cautions, pagination behavior, and truncation rules. The main gap is the missing default behavior when max_group_size is not supplied, and no explicit description of the overall return shape.

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 0%, so the description must compensate. It explains that username is required and that max_group_size=1 or 2 limits the UID sample per group, which gives real semantic meaning beyond the schema. It does not specify the default when max_group_size is omitted, but the core parameter intent is clear.

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 opens with 'Read eligible card groups for an explicit username', which states a specific verb, resource, and the required input. Among the many conflict_* siblings, this is the only eligible-cards tool, so the resource is differentiable even without opening the schema.

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 description implies when to use the tool: when an explicit username and eligible card groups are needed. However, it names no alternative tools and gives no exclusions or when-not-to-use guidance, so an agent gets only implied usage context.

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