apply_combat_profile

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

Discloses that the tool modifies engine state (sets enemy condition levers) and returns resulting stats. Warns that assumptions may inflate DPS if not aligned with build. No annotations exist, so description carries full burden and does so thoroughly.

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?

Description is well-structured: starts with main action, explains motivation, gives important caveats. No redundant sentences; every sentence adds value. Length is appropriate for the complexity.

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 no annotations and 7 parameters, the description covers purpose, when to use, behavioral implications, parameter meaning, and output expectation. It is sufficiently detailed for an AI agent to use 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?

Schema has 0% description coverage, but the description explains the boolean toggles as 'toggles' that represent build assumptions. It groups them together and provides context for each via examples (shocked, cursed). Could benefit from listing each parameter's role explicitly, but overall adds meaningful guidance.

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 applies a realistic boss-combat profile to reflect actual fight DPS. It explains why, referencing engine defaults and distinguishing from bare 'get_build_stats'. No ambiguity, and it differentiates itself from siblings like 'get_build_stats' and 'set_config'.

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: turn off toggles the build cannot sustain, explains tiers (None/Boss/Pinnacle/Uber). Tells when not to use (if build doesn't produce the effect). This helps the agent avoid overstating DPS.

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