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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that retrieval does not spend credits, which is useful context beyond the annotations, but it does not disclose pagination behavior, filtering behavior, or what the returned design listings contain.

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 short and front-loaded, but the first two sentences are largely redundant: 'List designs' repeats the annotation title, and 'List mail designs for your organization' extends it. The final sentence adds behavioral context.

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 simple read-only list endpoint, the description covers the core operation and notes that no credits are spent. However, it omits any context about the available filters and pagination, which are relevant to invoking this tool correctly despite being present in the nested schema.

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 description does not mention the query object or any of its filters such as page, size, search, status, or per_page. Context signals report 0% top-level schema description coverage, and although the nested schema has some field descriptions, the description itself fails to compensate by explaining how to use the filtering and pagination parameters.

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 states a specific verb and resource: 'List mail designs for your organization.' It is clear what the tool does, though it does not explicitly differentiate this list tool from the sibling single-design tool dealmachine_get_mail_designs_id or creation/patch/delete design tools.

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 listing intent is implied by 'List mail designs for your organization,' but there is no explicit guidance on when to use this tool versus fetching a single design by ID, creating a design, or modifying one. No alternatives or exclusions are named.

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