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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuine value beyond them by disclosing that the full body and every attached file are returned and that a caller-supplied ReliefWeb appname in _apiKey is required — an auth constraint the annotations do not convey.

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?

Front-loads the return payload and then tacks on usage flow and prerequisites; every sentence earns its place. The first sentence is dense with an enumerated content list, but it is informative rather than padding.

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 no output schema, the description carries the burden of describing returns and does so thoroughly, and the read-only safety profile is already covered by annotations. An agent has everything needed to call it correctly.

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 100%, so the baseline is 3. The description adds context beyond the schema by explaining the provenance of report_id ('from a reliefweb_reports result'), which helps the agent source a valid value; max_body_chars is left to the schema.

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 verb and resource — fetching ONE full ReliefWeb report — and enumerates exactly what it contains: body text, attachments, publishing orgs, countries/disasters, theme, format, and dates. It is clearly distinguished from reliefweb_reports, which returns only list-level titles.

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?

Explicitly says to use it 'after reliefweb_reports to read a situation report rather than only its title,' naming the sibling and the condition that selects this tool. It also states where to get the required id and the appname/_apiKey prerequisite, leaving nothing to inference.

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