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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The only added behavioral fact is the 'POST /v3/list_mats' endpoint, which is mildly useful (a read performed via POST) but says nothing about pagination, catalog size, or whether the list evolves over time. Most of the burden is left unaddressed.

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 short fragments with zero padding, but the terseness tips into under-specification rather than efficiency; there is no front-loaded statement of what the tool returns or how to narrow results.

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?

No output schema exists, so the description should explain what a 'mat' entry contains and how results are shaped; it does neither. For a list tool with an open-world catalog, an agent is left guessing about the response structure.

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 coverage is 100% with a single optional integer 'id' already documented as 'Only this mat id.' The description adds nothing about the filter, which is acceptable given full schema coverage — baseline 3 applies.

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?

Names the resource ('mats' with the clarifying gloss 'matting') and implies a listing, but the description is a noun fragment with no verb — the listing action comes only from the title. It is distinguishable from get_frame or list_media_types by the resource noun, so it avoids confusion with siblings, but barely.

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 statement of when to call this versus siblings like finerworks_get_product_details or finerworks_list_frame_collections, and no mention of when the optional id filter should be used instead of a full listing. Usage must be inferred entirely from the tool name.

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