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

With no annotations provided, the description carries the full burden. It describes the tool as a 'Fetch' operation, implying read-only behavior, and exhaustively lists the response contents. However, it does not explicitly state side effects, authentication requirements, rate limits, or performance characteristics. The read-only nature is only inferred from the verb, which is acceptable but not fully transparent.

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 front-loaded with the main purpose, but then runs on as one very long sentence enumerating every field and nested object. The detail is relevant, but the lack of structure (e.g., bullet points or separate paragraphs) makes it harder to parse quickly. It is adequately sized but could be better organized.

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?

Without an output schema, the description compensates by thoroughly enumerating the war statistics and all fields of active planets, including event details, attacking planets, and region data. It defines 'active planets' and 'active event information.' The only gap is the absence of exact JSON property names, but the semantic coverage is strong for a complex, zero-parameter tool.

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 takes zero parameters, and the schema confirms this with an empty properties object. The description adds no parameter semantics because none are needed. Per the baseline rule for 0-parameter tools, a score of 4 is appropriate.

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 action and resource: 'Fetch the current war status and active planets.' It clearly distinguishes this from sibling tools by focusing on war statistics and active planets, not planet lists, assignments, or dispatches.

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 communicates a clear context (retrieving war status), but it provides no explicit guidance on when to use this tool versus alternatives like get_all_planets or get_planet_details. It does not mention exclusions or preferred scenarios, so the guidance is implied rather than stated.

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