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 the safety profile is fully covered. The description adds the useful fact that this shelf is the exact set consumed by Match with what I have, but says nothing about return shape or ordering. That context is worth a 3, not more.

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 no filler, and the core resource ('materials marked as on hand') is front-loaded. The trailing parenthetical is slightly indirect but still informative rather than redundant.

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-parameter read tool with no output schema and fully covering annotations, the description supplies enough to call it confidently: what set is returned and how it relates to the matching workflow. Only a brief note on what the entries contain would improve it.

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 no parameters at all (empty schema, 0 required), so there is nothing for the description to disambiguate. Baseline 4 applies.

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 identifies the resource precisely ('the materials you marked as on hand in Glazecalc') and names the related consumer ('Match with what I have'), which lets an agent separate it from siblings like get_material or list_my_materials. It never states an explicit retrieval verb ('returns/lists'), so it falls short of the 5 bar, but the subject matter is unambiguous.

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 parenthetical link to 'Match with what I have' implies the tool is the source view behind that matching flow, which gives contextual usage. However, it never states when to reach for get_shelf versus list_my_materials, get_material, or match_with_what_i_have, and offers no exclusions.

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