build_list_skill_increase_options

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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral limitation: it does not consult skillIncreaseLevels itself, and it clarifies the fixed caps rule. However, it does not explicitly state that it is a read-only operation, though this is implied by 'list'.

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 sentences, front-loaded with the main purpose, and each sentence adds valuable context. No redundancy or fluff.

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 that the tool has an output schema, the description does not need to explain return values. It covers the core rule, the limitation, and the relationship to a sibling tool, making it complete for a list-like tool with good annotations.

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 one parameter 'character' that has no schema description, the description compensates by indicating that the character's current level and current ranks are required. It does not detail the full object structure, but the key inputs are identified.

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 what the tool does: lists which of the 16 core skills can be legally raised by one rank given current level and ranks. It distinguishes itself from build_get_level_up_choices by explicitly naming that as the confirmation tool.

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?

Provides explicit guidance on when to use this tool (to list legal skill increases) and when not to (to confirm availability, use build_get_level_up_choices). Also explains the fixed caps rule, clarifying that it applies regardless of class.

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