game_systems

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

With no annotations, the description carries the full burden of behavioral disclosure. It states what data is covered but does not mention output format, whether entries are sorted, whether zero-count systems are included, or any other operational behavior. This is a minimal statement of content, not of behavior.

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 a single focused sentence, starting with the core purpose and then enumerating examples. The parenthetical list is long but informative and not redundant. It is efficient and well-structured, though the list could arguably be trimmed without losing meaning.

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 zero-parameter tool, this is minimally adequate: it tells the agent what the tool provides (system names and counts). However, with no output schema, the description does not specify the response structure (e.g., JSON object, array), which leaves some uncertainty about how the result will be consumed.

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?

The tool has zero parameters, so the baseline of 4 applies. The description adds useful context about what the returned entity set covers, though parameter-specific explanation is moot.

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 identifies the resource (Castle Clash data systems) and the key information returned (entry counts), and the parenthetical list of systems gives concrete grounding. It distinguishes itself from sibling tools like list_heroes or get_hero by being a high-level catalog overview, though it lacks an explicit verb like 'return' or 'list'.

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?

Usage context is implied rather than stated: a user would call this to see the full scope of game systems and their counts, not to get details on a single system. No explicit guidance is given about when not to use it or which sibling tool to use instead.

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