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

Annotations already declare this as a non-idempotent write that is not destructive. The description goes further by naming the destination (Materials page) and stating the auth requirement ('an access token that can read and change your records'), which the structured fields do not convey. It does not describe error or duplicate-name behavior.

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?

Three sentences, front-loaded with the core action and effect, with no filler. Slightly padded by the auth sentence and the loss-on-ignition clause, which is already in the schema, but overall efficient.

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 five-parameter mutation with no output schema, the definition omits what the call returns (presumably the created material) and gives no duplicate-name or validation-failure behavior. The destination and auth context are covered, but the return surface is left unspecified.

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 60%; loi, analysis and language are already documented in the schema, while name and notes are not. The description restates the oxide-in-weight-percent format, adding little beyond the schema's own example, so it only partly compensates for the undocumented parameters.

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 and resource: it saves a material of the user's own into their Glazecalc account from an oxide analysis. The scope is narrow enough to separate it from add_to_shelf or add_notebook_entry, though it 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?

Downstream context is given ('Recipes can then use it by name'), which implies when to reach for it, but there is no explicit guidance versus update_my_material or list_my_materials, and no note that repeat calls create duplicates. Usage is implied rather than stated.

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