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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds the returned content domains, which is genuinely useful given there is no output schema, but it says nothing about behavior on unknown names, aliases, or discontinued items beyond listing them as fields.

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 compact sentence that front-loads the core idea ('One material') and then lists contents without filler. The trailing list is dense but every item is informative given the absence of an output schema.

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, the description is the only source of return-value information and it covers the main fields well. It is slightly incomplete on error/not-found handling and sibling routing, but adequate for a simple idempotent lookup.

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 100% and the single parameter is documented in-schema as 'Its name or alias.' The description adds no parameter semantics beyond that (it doesn't clarify alias matching or input normalization), so the baseline of 3 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 makes clear that this retrieves a single material's record and enumerates the content domains (oxides, LOI, discontinued status/replacement, vendors, hazards, data sheet source). It conveys verb+resource well, but never distinguishes itself from siblings like search_materials or match_from_materials, 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?

There is no explicit when-to-use statement and no mention of alternatives; the agent must infer that this is for fetching one known material by name vs. searching. No prerequisites or not-found behavior are described.

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