ddb_get_character

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

The description implies a safe read operation but does not disclose important behavioral traits such as authentication requirements, rate limits, or whether the returned character sheet is fully detailed. No annotations are provided, so the description carries full burden but falls short.

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 a single concise sentence that directly states the tool's purpose. No extraneous information is included, and it is efficiently front-loaded.

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?

While the description sufficiently covers basic retrieval, it omits information about the expected output (e.g., what 'full character sheet' entails). Given the lack of an output schema, the description could be more descriptive about the complexity and scope of the returned data.

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?

The input schema already provides descriptions for both parameters (numeric ID, name with substring match). The tool description adds no additional parameter meaning beyond summarizing they can be used for lookup. With 100% schema coverage, a baseline of 3 is appropriate.

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 clearly states the tool retrieves the full character sheet for a D&D Beyond character using either an ID or name. This verb-resource pairing is specific and distinguishes it from sibling tools like ddb_list_characters (listing) and ddb_get_campaign (different resource).

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 provides no guidance on when to use this tool versus alternatives, or when to use one parameter over the other. It does not mention prerequisites (e.g., needing a login) or when to prefer ddb_list_characters first.

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