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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered; the description adds real content semantics beyond that — per-100g nutrient basis, per-nutrient `microsOrigin` provenance, 'as bought' traits, and the crucial 'null = none known' meaning for certifications. It omits ordering, recency window, and how 'frequent' is computed, which keeps it off a 5.

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, both front-loaded with the highest-value information (what the list is, then how to reuse it). The dense field enumerations are justified because no output schema exists to carry them.

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 and 0% parameter coverage, the description does the heavy lifting on return shape and largely succeeds — nutrient basis, provenance, traits, brand/certifications. Remaining gaps are ordering/pagination semantics and the undocumented `limit`.

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?

One optional `limit` parameter with 0% schema description coverage: the schema supplies only the 1–100 bounds, and the description never mentions the parameter, its default, or what happens when it is omitted. With so few parameters the schema does most of the work, so a mid-scale 3 is fair.

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 resource with clear scope: the signed-in user's *most frequently logged* foods, plus the nutrient/provenance/trait payload. An agent can distinguish it from joiva_search_foods (arbitrary lookup) and joiva_list_meals by the 'frequent' qualifier, though the description never names those siblings explicitly.

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?

The sentence 'Logging with these names/subTypes reuses the existing items' implies the intended workflow — fetch canonical names here before calling joiva_log_food — but the guidance is oblique and there is no explicit when-to-use/when-not or named alternative such as joiva_search_foods.

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