skill_xp_info

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

No annotations provided. Description states two modes based on input, but does not disclose behavior if both parameters provided, error conditions, or return format details. Missing edge case handling.

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?

Single sentence, front-loaded with verb and resource. No wasted words. Efficient and to the point.

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?

No output schema, but description mentions what the tool returns for each parameter. Combined with schema, it covers the needed functionality. Lacks mention of possible output structure or errors.

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% with clear parameter descriptions. Tool description adds only a summary, no new semantics beyond what schema already provides.

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?

Clear verb 'Get' and specific resources 'XP required for a level' or 'current level from XP'. Distinguishes from siblings like get_stats which provide raw stats, not conversion. Two clear use cases.

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?

Implies usage for XP-to-level conversion, but no explicit when-to-use or when-not-to-use compared to alternatives like get_stats. No exclusions or context provided.

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