list_size_presets

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

With no annotations, the description carries the full burden. It implies a read-only operation ('List') and provides context ('so the canvas matches the target channel'), but it does not disclose return format, pagination, authentication requirements, or any limitations. This is adequate but lacks depth for a tool with no structured safety hints.

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 exactly two sentences, with the primary action front-loaded. Both sentences are informative: the first states what the tool does, the second explains when to use it. There is no redundant or filler content.

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 simplicity of the tool (one optional parameter, no output schema), the description adequately covers its purpose and use case. It does not describe the exact structure of the returned presets, but the tool's function is clear and the missing details are minor in 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 schema already documents the only parameter 'category' with a description ('Optional preset category filter') and an enum covering all categories. The tool description adds no additional detail beyond the schema, so it stays at the baseline for 100% coverage.

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 clearly states the tool's action: 'List canvas size presets' and specifies the resource (canvas size presets) plus the categories (social, video, blog, presentation, and print). This distinguishes it from sibling tools like get_page_layout or get_design_context, which serve different purposes.

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 provides explicit when-to-use guidance: 'Call this before creating a design document so the canvas matches the target channel.' This clearly explains a key use case, but it does not mention when not to use the tool or name alternative tools, falling short of the highest standard.

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