parse-ddb-character

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

With no annotations, the description carries full burden. It discloses key behaviors: pure and deterministic, deduping ability scores, resolving choices, no compendium lookup, never invents content, and returns an unresolved list. This comprehensively informs the agent of the tool's behavior.

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 dense but well-structured, front-loading the purpose. Each sentence contributes meaningful information. It is slightly long but remains focused and informative, earning a 4 for conciseness.

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?

Given 3 optional parameters, no output schema, and no annotations, the description covers all necessary aspects: input modes, processing details, return shape ({success, plan, message}), and what the plan contains (abilities, classes, spells, etc.). It is complete for an agent to use correctly.

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%, so baseline is 3. The description adds value by explaining that url/characterId fetch public characters via v5 endpoint, and json is for private characters (common case), including acceptable formats (full envelope or inner data, parsed object or string). This goes beyond the schema descriptions.

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 'Parse a D&D Beyond character into a normalized, name-bearing plan for the ddb-import skill,' specifying the verb 'parse' and the resource 'D&D Beyond character'. It distinguishes from sibling tools by focusing on external data parsing and plan generation, not direct PC creation or advancement.

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 explains two usage modes: fetching a public character via url/characterId or accepting pasted json for private characters. It explicitly states what the tool NEVER does (handle a cookie) and gives context on subsequent steps (skill canonicalizes names). While it doesn't name specific alternatives, the context suffices.

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