build_list_equipment

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

With no annotations, the description carries the disclosure burden. It reveals that STARTING_WEALTH_GP is returned alongside results as a reminder, explains the default behavior of include_legacy, and references the legacy filter SQL, adding transparency about filtering 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 main purpose is stated in one sentence, followed by context about starting wealth and a parameter detail. The reference to `_legacy_filter_sql` could be trimmed, but the description remains focused and 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?

The tool is a simple list operation with an output schema. The description covers filtering, default behavior, and the starting wealth caveat, making it sufficient for an agent to select and invoke 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?

With 0% schema description coverage, the description compensates by naming the filter criteria ('name substring, item type, and/or maximum price') and explicitly explaining include_legacy's default and meaning. All four parameters are effectively documented.

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 'Browse the equipment pack (weapons, armor, shields, gear) by name substring, item type, and/or maximum price.' This clearly identifies the resource (equipment) and the verb (browse), and distinguishes it from sibling tools that list other character options like ancestries or classes.

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 does not explicitly mention alternatives, but the context of sibling tools (e.g., build_list_ancestries, build_list_classes) makes it clear this is for equipment. It also sets expectations for use during character building by referencing starting wealth and legacy filtering.

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