manage_combat

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

The annotations are all false (readOnlyHint, destructiveHint, etc.), providing no safety or side-effect profile. The description does not disclose potential destructive actions, prerequisites, or consequences of creating/overwriting combat configs, which is significant for a mutation 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?

One sentence covering key capabilities with no redundancy. It is front-loaded and efficient, though it could be slightly more structured to list actions.

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 86 parameters, 39 actions, and no output schema, the description is insufficient. It doesn't explain how to invoke actions, what the required 'action' parameter means, or what the tool returns. Agents would struggle to understand request composition despite the schema.

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 description coverage is high (86%), so the schema already documents most parameters. The description adds broad thematic context (hitscan, melee) but doesn't detail any specific parameter relationships or requirements, so it meets baseline 3.

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 uses specific verbs 'create' and 'configure' and names concrete combat resources (weapons, damage types, hitboxes, reload, melee). It clearly distinguishes from siblings like manage_asset or manage_blueprint by focusing on combat mechanics, though it is broad and could be more specific.

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 explicit guidance on when to use this tool versus alternatives. It doesn't mention exclusions or prior steps. The intended usage is only implied by the tool name and description summary.

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