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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. Description adds that ids are exact strings for build_logo_editor_link, create_text_logo_project and update_project, and mentions output includes category and Pro flag. This is useful context beyond annotations, but no additional behavioral traits like pagination or errors are disclosed. Since annotations cover safety, a 4 is appropriate.

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?

Three sentences with no redundancy. The purpose is front-loaded, then output/usage details, then exclusion with alternative. Every sentence adds value.

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?

Given the tool has an output schema, the description need not detail return values. It covers when to use, what it returns (category, Pro flag), and how ids are used in other tools, plus an exclusion. Complete for a simple list tool.

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 the category parameter fully described by enum and description. The description mentions categories in passing but adds no new meaning about the parameter beyond the schema. 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?

States a specific verb 'list' with resource 'materials' and clarifies it returns material ids, category, and Pro requirement. It also distinguishes from browse_looks by explicitly saying not to use for showing looks. Clear purpose with differentiation.

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?

Explicitly says 'Use when you need a material id' and provides a positive use case. It also gives a negative case: 'Do not use to show the user what a look is like; browse_looks has example images.' Names the alternative tool and the condition that selects it.

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