fishing_xp_forecast

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

With no annotations, the description carries the full burden. It provides the XP formula and mentions multiplicative stacking, but does not explain how save XP is retrieved, how the save_path parameter is used, or what happens if no save is configured. The note reference is unresolved, leaving behavior partially unspecified.

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 two sentences with a formula, front-loading the purpose. However, the unresolved note reference ('see `note`') adds an element of confusion and assumes external knowledge, slightly detracting from 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 the tool has 9 parameters and an output schema, the description does not explain what the tool returns (e.g., number of catches, detailed breakdown). The formula and stacking info are useful but omit key behavioral details like save file requirements or error handling.

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 the baseline is 3. The description adds value by explaining the XP formula and how multipliers (perfect, treasure, legendary) stack, which clarifies the meaning of those boolean parameters beyond the schema's basic 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 the tool calculates 'Catches needed to reach a target fishing level' and provides the XP formula, which is specific and distinguishes it from siblings like 'skill_xp_forecast' or 'fish_available'. However, the reference to a missing note reduces clarity slightly.

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?

No guidance is given on when to use this tool versus sibling tools like 'skill_xp_forecast' or 'fish_available'. The description does not mention any conditions or exclusions, leaving the agent without context for appropriate invocation.

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