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

No annotations are present, and the description does not disclose whether the operation is read-only or has side effects. There is no mention of output behavior, errors, or side effects such as caching or state changes.

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 short sentence, but it lacks necessary details. It is concise in wording but not in conveying substantive information, leaving the reader with many questions.

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?

There is no output schema and no description of what 'standardized information' includes. The tool is incomplete for an agent to understand what to expect in the response, such as fields, format, or possible status codes.

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 only parameter 'query' is described as 'The African term to resolve' which is minimally informative. It does not specify expected format (e.g., single word, phrase, language), possible values, or any constraints beyond minLength.

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 states it resolves an African word or food term but 'resolve' is ambiguous and does not clarify whether it means lookup, disambiguation, or translation. It does not differentiate from the sibling tool resolve_african_dish, which likely handles dish names specifically.

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?

No guidance is provided on when to use this tool versus alternatives like search_african_foods, find_foods_by_country, or resolve_african_dish. The description lacks any context for selection criteria.

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