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 it is unusually transparent: it declares one logical GET request, no auto-fetching of continuation pages, wagon limits of 100 rows and 256 KiB, truncation reporting, refusal of oversized records, and a caveat that declared filters may be forwarded without guaranteed effectiveness. This is genuinely useful behavioral context.

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 purpose is front-loaded and the content is dense rather than padded, but the middle section mixes flag behavior, pagination policy, filter caveats, and limit details into a single wall of text. It is compact enough, yet the lack of visual structure makes it harder to scan.

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 no output schema, the description covers request behavior, limits, truncation, and oversized-record handling well. However, it omits the meaning of most filters and does not describe the shape of the returned sections, leaving meaningful gaps for a tool with 12 parameters.

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 0%, so the description needed to define all 12 string parameters, but it only clarifies three flags (only_config, only_wagons, exclude_wagons) plus a generic 'forwarded as supplied' caveat. Parameters such as lore, only_stats, only_conflict, and the remaining exclude_* flags are left to inference, which does not sufficiently compensate for the coverage gap.

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 opening sentence identifies a specific operation ('Read') and enumerates the exact resource bundle: conflict configuration, current conflict, player statistics, and wagons for a username. It is clear what the tool returns, but it does not explicitly contrast it with related conflict_* siblings such as conflict_players or conflict_wagon.

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?

There is no guidance on when conflict_status should be chosen over conflict_wagon, conflict_players, or conflict_seasons. Statements like 'required inputs reflect tool policy' are policy notes, not usage conditions, and no alternatives or exclusions are mentioned.

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