conflict_status

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

With no annotations, the description carries the full burden and does so exceptionally well. It discloses flag behavior, that only_config=true does not reduce the response, the single-GET behavior, lack of continuation-page auto-fetching, local wagon limits, truncation reporting, and refusal of oversized records without partial fields. This is far beyond typical descriptions.

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 dense and information-rich, with no filler sentences. It is slightly run-on and would benefit from clearer separation, but every sentence adds meaningful operational detail and the core purpose is front-loaded.

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 complexity (12 parameters, no annotations, no output schema), the description covers a remarkable amount: purpose, flag behavior, request count, pagination behavior, result limits, truncation, and oversize handling. It still leaves the full response shape and the semantics of several flags implicit, but it is substantially complete for an agent to invoke the tool safely.

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 0%, so the description must compensate. It explains only_config, only_wagons, and exclude_wagons with concrete examples, and adds a general caveat that other declared filters are forwarded without implied effectiveness. However, most of the 12 parameters (lore, only_stats, exclude_stats, only_conflict, etc.) are not individually described, leaving an agent to infer their semantics from the naming pattern.

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 opens with a specific verb and resource: 'Read conflict configuration, current conflict, player statistics and wagons for an explicit username.' This clearly identifies the tool's scope and differentiates it from sibling conflict_* endpoints by describing a combined status read rather than a single list or rank lookup.

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?

The description makes the intended use clear: call this when you need a bundle of conflict-related data for a specific username. It does not explicitly name alternatives or state when not to use it, but the context is strong enough that an agent can infer when it applies.

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