ddb_list_campaign_characters

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

With no annotations provided, the description carries the full burden. It adds a useful behavioral detail (campaignId default), but does not explicitly indicate that this is a read-only operation (though 'list' implies it), nor does it disclose error handling, response format, or authentication. This is a minor gap for a simple list tool.

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 description is two concise sentences, front-loaded with the action. The default behavior is stated succinctly, with no unnecessary words or repetition.

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 single-parameter tool with no output schema, the description provides the core behavior and the parameter default. It does not mention the return format or error cases, but these are not essential for an agent to successfully invoke the tool. It is minimally complete.

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 explain the parameter. It mentions the default value of campaignId, adding context, but does not explicitly state what campaignId refers to (though the tool name and context make it obvious). The description partially compensates for the missing schema guidance.

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 states a specific action ('List') and resource ('player characters in a DDB campaign'). It clearly differentiates from siblings like ddb_get_character (single character) and ddb_list_campaigns (campaigns) by specifying 'all' characters.

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?

It provides usage context by noting the campaignId default to the DDB_CAMPAIGN_ID env var, but does not explicitly mention when to use this tool versus alternatives or any exclusion conditions. The use case is implied by 'all player characters' but not contrasted with sibling tools.

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