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

With no annotations, the description carries the full burden but does disclose two meaningful traits: the roll is 'engine-rolled' (server-authoritative, not client-supplied) and 'public' (visible to others). It does not say whether re-rolling is permitted, whether the result expires or is bound to a table/character, or what happens if a character is created without using the returned id.

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 tight sentences with zero filler. The operation and its output token are front-loaded, and the handoff instructions for ad_create_character follow immediately.

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?

No output schema exists, so the description must explain the return value — and it does, naming wealthRollId and its consumer. What remains unstated is lifecycle: whether the id is single-use, how long it stays valid, and whether each call produces a fresh roll.

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 coverage is 100% and the single parameter is already documented ('Class name, exactly as listed in the build options'), so the baseline of 3 applies. The description's reference to 'a class's SRD starting wealth' corroborates the valid input domain but adds no new syntax or constraint detail.

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 and resource ('Roll a class's SRD starting wealth') and immediately frames the result as a token ('Returns a wealthRollId') rather than a raw number. This clearly separates it from siblings like ad_get_rolls (retrieval) and ad_create_character (the actual character creation).

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?

Names the alternative path explicitly: use this 'to take the starting-wealth path instead of the equipment packages,' and tells the agent exactly what to do next with the result. It lacks a negative case (e.g. when NOT to roll, or whether a roll can be re-done), so it falls short of full when/when-not coverage.

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