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

Annotations are empty, so the description carries the full burden of behavioral disclosure. It conveys only that the tool returns a complete unfiltered listing and that records are 'standardized', but it does not disclose the return format, pagination behavior, whether unstandardized or unclassified records are excluded by the 'standardized' filter, or any performance implications of listing all records. For an unannotated tool, this is a significant gap.

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?

A single sentence with zero redundancy, front-loading the verb 'list' and the resource immediately. Every word earns its place, and no filler or irrelevant detail is present.

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 tool is simple (zero params), but there is no output schema, so the description should compensate by describing the shape of a dish record or the return format. It does neither, and it leaves the meaning of 'standardized' undefined. It is minimally adequate for a simple list tool, but the lack of any return-format disclosure leaves an agent guessing about the result structure.

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 tool takes zero parameters, so the schema covers everything (100% coverage trivially) and there is nothing for the description to explain. Per the rubric, a zero-parameter tool earns a baseline of 4; the description adds no parameter information, which is acceptable since no parameters exist to document.

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 a specific verb ('list'), a specific resource ('standardized African dish records'), and a scope ('all... in the AfriResolve knowledge base'), which clearly distinguishes it from the filtered find_dishes_by_country, find_dishes_by_ingredient, and find_dishes_by_region siblings. It stops just short of a 5 because it does not explicitly name any sibling it is not, leaving differentiation to inference from the 'all' wording.

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 given on when to use this tool versus its siblings. The description never mentions that find_dishes_by_* and search_african_foods are the filtered alternatives, nor does it state when a full unfiltered listing is appropriate. The 'all' wording implies unfiltered usage, but this is only implicit and no exclusions or alternatives are named.

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