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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds that the catalog is authoritative and public, but mostly restates 'read-only' without adding deeper behavioral context beyond the annotations.

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?

The description is a single front-loaded sentence with no filler. Every phrase contributes meaning: the action, the resource, and the read-only nature.

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, read-only discovery tool with rich annotations and sibling context, the description is largely sufficient. It doesn't need to enumerate return shape since it is a free-form catalog match, though a bit more detail about output would push it higher.

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?

The intent parameter has 0% schema description coverage, so the description must compensate. The phrase 'user problem' tells the agent that intent should contain the user's request, but it does not specify format, examples, or constraints beyond the schema's maxLength.

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?

The description uses a specific verb, 'Match', with a clear object: the authoritative public Evercraft commercial catalog. It signals a discovery/semantic-matching role that is distinct from siblings like get_evercraft_offers or prepare_evercraft_checkout.

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 description conveys that the tool maps a user problem to catalog entries, which implies when to use it. However, it never explicitly states when not to use it or names alternatives such as get_evercraft_offers or get_evercraft_order_status.

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