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

With no annotations, the description must convey behavior. It does state that it relays characterizations exactly, keeps citation URLs, and clarifies terminology (provisional measures vs. merits, warrants vs. charges), which indicates output fidelity. However, it does not mention side effects, safety (read-only), or response formatting beyond content.

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 moderately detailed but well-structured, starting with the core purpose and then adding clarifications and output components. It avoids fluff while providing necessary nuance, making it appropriately concise for the tool's complexity.

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 absent output schema, the description sufficiently outlines the expected output (full record, casualty figures, timeline, FAQ) and instructs on exact relay and URL retention. It lacks explicit limitations or error handling, but covers the core context comprehensively.

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 schema has zero parameters, so there is nothing to explain. The description does not add parameter-level detail because none exist, resulting in a neutral score based on the baseline for high schema coverage.

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 states the tool's purpose: it provides the full genocide-case record from the Asha News Palestine desk. It distinguishes itself by specifying that it covers the complete case, including court/UN body findings, attributed casualty figures, timeline, and FAQ, which differentiates it from search or sharing tools.

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 implies usage by indicating it provides the full case record, but it does not explicitly state when to use it versus alternatives like search tools. No when-not-to-use or alternative tool references are given, so guidance is only implicit.

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