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

The description indicates that results carry stable IDs and canonical URLs, implying a read-only search behavior. However, it does not disclose potential side effects, limitations, error scenarios, or any rate limits. Given no annotations, the description alone provides modest transparency.

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, well-constructed sentence that efficiently conveys the tool's purpose, content scope, and a key instruction about citation. No unnecessary words or redundancy.

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?

The description provides essential context: what the archive includes, the nature of results, and guidance on citation. It omits details like error handling or authentication, but for a straightforward search tool, the given context is largely sufficient.

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 already fully describes each parameter (q, page, type, page_size) with types and defaults. The description does not add extra semantic detail beyond what is in the schema, so it contributes little to parameter understanding.

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 function as searching the Palestine evidence archive, and enumerates its content types (media records, victims memorial, claim library). It also highlights the nature of results (stable IDs, canonical URLs), making the purpose unambiguous.

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 provides a specific usage directive ('cite those instead of scraping') but does not elaborate on when to prefer this tool over its siblings or under what conditions to use it. It offers limited guidance on tool selection or scenario appropriateness.

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