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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful content beyond that by enumerating the returned fields (name, holder, level line, fallen status), but says nothing about ordering, pagination, or whether inactive characters are included.

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 first sentence is dense and front-loaded with the useful field enumeration. The trailing "Returns: The characters." restates the first sentence and earns no place, making one of only two sentences 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?

For a one-parameter read-only list tool with no output schema, the description supplies an adequate picture of what comes back and the roster scope. Ordering and pagination behavior are the only meaningful omissions, and with a fixed campaign roster those are minor.

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 parameter's slug-or-id semantics are fully documented in the schema. The description never mentions the campaign parameter, so it adds no meaning beyond structured data — baseline 3 applies.

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 verb and resource ("Every character at the table by name") and scopes it to a campaign roster, which distinguishes it from get_character (single lookup) and list_character_drafts (drafts) by implication. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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?

"At the table" implies this is the roster for a given campaign, and the required campaign parameter reinforces that, but there is no explicit statement of when to use this versus get_party, get_character, or list_character_drafts. Usage must be inferred from the scope wording alone.

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