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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description adds value by disclosing the payload: source, precision, nearest infrastructure, and nearby reports. It also flags that only public reports are returned, which is genuine behavioral context the annotations do not carry.

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?

A single front-loaded sentence that identifies the resource, the identifier source, and the returned fields with no filler. Every clause carries information an agent would otherwise have to guess.

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?

With one parameter and no output schema, the description covers the key gaps: what the id is and what the response contains. It is slightly thin on failure modes (missing/private reports) but otherwise sufficient for correct invocation.

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, and it does by explaining that the integer id is the number embedded in the warstrikes.com/event/<id>-… URL rather than an arbitrary identifier. That is meaningful guidance beyond the bare 'integer, minimum 1' in the schema, though it omits error behavior for nonexistent ids.

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 resource (a single public report) and scope (lookup by id), which distinguishes it from the list-oriented sibling search_reports. The verb is carried by the name/title rather than the sentence, so it falls just short of a full 5.

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 phrase 'One public report by its id' implies single-record retrieval versus the sibling search tools, but it never explicitly says to use search_reports to discover an id or what to do when the id is unknown. Usage 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.