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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: this is a pure text-in/text-out transform with no image processing, which is the main behavioral surprise an agent could hit.

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, both load-bearing: the first defines the transform and its output shape, the second kills the image-input misconception. Nothing is redundant or buried.

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 return field details needn't be restated, and annotations cover safety. The definition is essentially complete for calling it, though it does not hint at whether ocrConfidence or sourceImageName affect results, a minor gap for a 3-parameter 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 100%, so ocrText, ocrConfidence and sourceImageName are already documented in the schema. The description only reinforces which parameter to send ("send the label text") and says nothing about how confidence or source image name are used. Baseline 3 is appropriate.

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 (turn/parse) and a specific resource (reagent bottle or kit label text) and names the concrete output fields (product name, catalog number, lot, expiry, concentration, storage). An agent can immediately tell this is a text-to-structured-fields parser rather than an OCR or file-fetch tool.

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?

Explicitly bounds the input: "Parses the provided text only; send the label text, not an image." That exclusion prevents the most likely misuse. It stops short of naming a sibling (e.g., fetch) as the source for obtaining OCR text, so routing to an alternative is left implicit.

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