list_available_shapes_and_fonts

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

With no annotations, the description must carry the full behavioral disclosure burden. It does convey read-only listing behavior and the scope of what is listed, but it says nothing about ordering, availability/static nature, or return shape. There is no contradiction, but behavioral detail is minimal.

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?

It is a single, front-loaded sentence that names the action and the full set of resources without filler. 'Typography font styles' is slightly repetitive but does not hurt clarity.

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 zero-parameter listing tool, the description is nearly complete: it enumerates exactly what the agent will receive. The only gap is some explicit guidance about how the listed options connect to create_custom_cutter_checkout, though the sibling names and 'for personalized cutters' supply enough context.

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 tool has zero parameters, so the schema already exhaustively documents them (100% coverage). The description adds scope context by naming the categories returned, which is all that parameter semantics can do here; baseline 4 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?

The description opens with a specific verb 'List' and names three concrete resources: supported 3D shapes, typography font styles, and recommended occasions for personalized cutters. This clearly distinguishes the tool from create_custom_cutter_checkout and get_cutter_specifications, which imply different actions.

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 phrase 'for personalized cutters' gives some context, but the description never states when to choose this tool over siblings or what the output should be used for. Usage is only implied by the name and the available sibling list, not explicitly guided.

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