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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the safety profile is covered. The description adds genuine value by warning that RGB values are community approximations rather than calibrated measurements, but says nothing about not-found handling or what fields are returned.

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 front-loads the action and appends the data-quality caveat, with no filler. The caveat is separated by a semicolon, which keeps the primary purpose first.

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 hints that RGB data is returned but does not enumerate the response fields or clarify what the lookup yields for a given code. Adequate for a simple lookup, but leaves the caller guessing about the return shape and the brand parameter's effect.

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 burden, yet it never explains the 'brand' parameter (enum mard/mard221) or the code format constraints (1-8 characters). An agent must infer the role of the second parameter entirely from the schema enum.

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 ('Look up') and resource ('a specific MARD bead code'), so the operation is unmistakable. It does not name or differentiate from the siblings convert_image_to_pattern and get_conversion_guide, though those are clearly different operations.

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 guidance on when to use this versus the sibling tools, and no note on prerequisites or what happens when a code is not found. Usage is only implied by the verb 'look up'.

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