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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so safety is covered. The description adds value annotations don't carry: the result is a shelf listing where each material nests its bottles and a 'running low' flag. It still says nothing about pagination or ordering.

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, no filler, and the usage triggers are front-loaded. The payload enumeration is packed into one dense clause but every listed field is informative rather than padding.

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 zero-required-parameter read tool with no output schema, the description usefully enumerates the return fields, which covers the missing output schema. However the undocumented 'query' parameter remains an unresolved gap, so an agent still cannot call the tool fully correctly from the definition alone.

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 description coverage is 0% and neither parameter is described anywhere. 'lowOnly' is only obliquely hinted at by 'what is in stock or running low', and the 'query' parameter is entirely unexplained — an agent cannot tell whether it is free-text search, a material name, or a filter. With 0% coverage the description needed to compensate and largely does not.

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 (lists) and resource (materials on the user's shelf) and even enumerates the returned facets: bottles, strength, solvent, stock, price, supplier, lot, running low. That is far beyond a tautology. It never names a sibling (get_shelf_material, search_materials) to sharpen the boundary, so it stops short of a 5.

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?

Gives concrete triggering conditions: the user asks what they own, what is in stock or running low, or the agent needs a first step before suggesting makes. That is real usage context. It does not state when NOT to use it or name an alternative (e.g., get_shelf_material for a single item), so it is short of 5.

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