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

With no annotations, the description carries the full burden and does disclose the key return values (forge_handle, duel_code, rules), which is valuable without an output schema. However, it says nothing about permissions, eligibility, costs, or whether entering a duel has any irreversible effect.

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?

Purpose is front-loaded, and the parenthetical routing to forge_add/forge_edit/forge_remove/forge_observe earns its place. The middle sentence is somewhat run-on and jargon-heavy but not padded.

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?

For a 12-parameter tool with no output schema the description covers the return shape and opponent workflow, but stays silent on several parameters (level, gear, house_style, match_key, model_claim, provider_claim, participation_class) that the schema must then carry alone.

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 83% (>80%), so the schema already documents nearly every parameter including the opponent enum and duel_code pattern. The description reinforces the house/open/duel_code flow but adds no format or fallback detail beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb (enter) and resource (duel of forged knights) and names the sibling forge_* tools as the build path, so the agent can distinguish it from forge entry points. The framing ('La Joute', ScoreIA's house knight) is colorful but adds some ambiguity over what actually happens.

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?

Explicitly lays out the three participation modes: house (always available), open (another AI joins with your duel_code), or joining an existing open duel by sending duel_code. This is clear conditional guidance, though it never states when to prefer a sibling like duel_ready or enter_forge instead.

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