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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description still adds genuine value by disclosing the two-branch outcome: stored catalog data when found, otherwise a link to analyze the product on greenercloset.com — a fallback an agent needs to relay to the user. It stops short of describing result formatting or latency, but that is minor given the output schema exists.

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?

Front-loaded with the trigger condition, followed by expected returns, then exclusions — a logical order an agent can scan. The single long sentence is dense and slightly run-on, but every clause (query types, sample utterance, fallback, two exclusions) earns its place.

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 one-parameter lookup with a full output schema and complete annotations, nothing an agent needs to select or invoke it is missing: trigger conditions, disambiguation from check_fabric_label, and the not-in-catalog behavior are all present. Return-value detail is appropriately deferred to the output schema.

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?

With one parameter at 100% schema coverage and a schema-side example URL plus length bounds, the schema does the heavy lifting, so baseline 3 applies. The description reinforces that the input must be a full product-page link rather than label text, but adds no format or normalization guidance beyond the schema.

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 ("Check a clothing product") and immediately specifies what it returns: Greener Closet's stored fiber breakdown and score, with a fallback when the product isn't in the catalog. It also names the sibling it is not (check_fabric_label), so an agent can separate it from alternatives without opening any schema.

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?

Explicit when-to-use conditions are given (user shares a product-page link and asks about materials, polyester/synthetics, 100% cotton, or sustainability), complete with a sample utterance. It also states two clear exclusions — pasted label text goes to check_fabric_label, and URL-less product descriptions are out of scope — leaving nothing to inference.

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