calc_items_to_level

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

No annotations are provided, so the description must fully disclose behavior. It merely states the calculation but does not mention assumptions (e.g., linear XP per action), use of OSRS XP table, edge cases like level 99, or potential errors (e.g., invalid skill name). This is insufficient for a calculator tool.

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 sentence with 15 words, highly concise and front-loaded with the core purpose. Every word contributes useful information.

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?

Without an output schema, the description should indicate the return value format (e.g., integer count) or list possible results. It does not. Additionally, it omits error conditions or edge cases. Given 5 parameters and no annotations, the description is incomplete for safe use.

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 all parameters have descriptions. The description adds minimal new meaning beyond reinforcing the role of xp_per_item. It does not explain the mutual exclusivity of current_level and current_xp, but the schema already covers that. Baseline 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 calculates the number of actions needed to reach a target skill level given XP per action. It uses a specific verb (calculate) and resource (items/actions), and distinguishes from sibling tools like skill_xp_info which only provide XP requirements.

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 implies when to use: when you need to know the count of actions for leveling. It does not explicitly state when not to use or provide alternatives, but the context among siblings makes the use case clear.

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