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

Annotations already mark it read-only, and the description adds meaningful behavioral context: the score is population-weighted momentum vs a 60-90-day baseline, updates daily, and returns specific fields. It also clarifies the scope (24 WFP HungerMap countries) without contradicting annotations.

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?

Two sentences of dense, front-loaded information; the first sentence conveys the core function and return fields while the second gives usage context and update cadence. It is slightly complex but every phrase earns its place.

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?

For a read-only single-parameter tool, the description covers the score definition, country scope, baseline window, return fields, update frequency, and usage scenarios. The absence of an output schema is compensated by listing the main return fields. Minor gaps like potential limitations or handling of missing data prevent a 5.

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% with a self-explanatory 'days' parameter, so baseline is 3. The tool description does not mention the optional history feature at all, leaving the schema to carry that meaning; no additional semantic value is added beyond 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?

The description clearly states the tool returns a specific 0-100 food-insecurity pulse score with methodology and return fields. The verb 'Returns' and the resource ('food-insecurity pulse score') make its function unambiguous, and the inclusion of countries and baseline distinguishes it as a specialized global index among many siblings.

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 identifies five use-case triggers: global hunger trends, food-crisis momentum, humanitarian conditions, and timing early-action funding/aid positioning/ag-commodity reviews. However, it does not state when not to use it or name alternative tools, so it falls short of a full 5.

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