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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuinely new behavioral context not in the annotations: 'This does not access an account,' which tells the agent no authentication or account scoping is needed. It says nothing about caching, ordering, or return shape, though the output schema covers results.

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 sentences, zero filler. The content of the list is front-loaded and the account-access caveat is appended where it adds the most value without padding.

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 parameters, an existing output schema, and full annotation coverage, the description only needs to convey what is returned and any caller prerequisites, both of which it does. It is complete in practice, though it could note that these are static platform options independent of any saved design.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies a no-argument enumeration by listing the categories returned rather than any filtering inputs.

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 ('List') and enumerates the exact resource contents (fonts, bases, colors, thickness ranges), which is far more informative than a bare 'list options'. The word 'supported' implicitly separates it from list_saved_designs, but the description never names that sibling or explicitly contrasts static catalog data with user-owned designs.

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?

'before configuring a 3D name' tells the agent exactly where this fits in the workflow, namely as a prerequisite lookup ahead of create_design. It does not name alternatives or state exclusions, so it stops short of the explicit when-not/alternative routing a 5 would require.

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