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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds genuinely non-obvious context beyond them: the data is free, cleared_with_attribution, requires an INFORM (EU JRC/ACAPS/OCHA) CC BY 4.0 credit, and that Tripwire only maps published scores to ISO codes without altering them. It stops short of stating update cadence specifics or failure behavior, so it is strong but not exhaustive.

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-loaded with the use case, then the licensing and attribution constraints, then a source URL — a sensible order. It is dense but each clause carries operational weight (attribution is a compliance requirement); the only mild redundancy is the paired "Free. License: cleared_with_attribution."

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 it does so at a high level — a 1-5 severity value or a list of scored crises. It does not describe the fields in the crisis list or response envelope, which is the remaining gap for a one-parameter lookup 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?

Schema coverage is 100% and the single country parameter already documents the ISO 3166-1 alpha-2 format, so baseline would be 3. The description adds real value by clarifying that supplying a country yields its monthly score while omitting it returns the full list of scored crises, and that scores pass through unchanged from the source.

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: retrieves monthly INFORM humanitarian crisis severity (1-5) for a country, or the current list of scored crises. The two operating modes are named explicitly, and no sibling tool in the list overlaps with humanitarian severity data, so the agent can select it confidently.

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?

"Use this when you need the monthly INFORM humanitarian crisis severity... or the current list of scored crises" gives a clear trigger condition covering both call shapes. No exclusions or alternatives are offered, but none of the listed siblings plausibly compete, so the guidance is sufficient rather than complete.

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