baker_quick_load

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

Annotations already declare readOnlyHint=false / destructiveHint=false, and the description adds genuine non-obvious behavior: an unmatched stem produces a group missing a High entry and an empty bake. That is exactly the kind of failure mode an agent needs to know, and 'check the returned groups' tells it how to detect it. It does not mention what happens to pre-existing objects or whether the operation is reversible.

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 tight sentences, zero filler, with the pairing rule front-loaded ahead of the failure caveat. Every clause carries information.

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?

An output schema exists, so explaining return values is not required, and the annotations cover the safety profile. But for a two-parameter tool with 0% schema coverage, the description leaves the agent guessing what 'path' points at and what 'baker' selects — a meaningful gap before it can actually call the tool.

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%, so the description must carry the parameter burden and it does not: 'path' is never explained (model file? directory of low/high pairs?) and 'baker' (integer|string|null) is never mentioned at all. Two undocumented parameters with no compensating prose.

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 (load), resource (a model), and the mechanism (Quick Loader with <stem>_low / <stem>_high pairing into one group per stem). That is more informative than the name alone, though it does not explicitly distinguish itself from the similar scene_import_model sibling.

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 naming convention acts as a clear precondition for correct use, and the description tells the agent to verify the returned groups afterward. It stops short of naming an alternative (e.g. scene_import_model) or saying when not to use Quick Loader.

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