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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description's 'without changing records or spending credits' restates the read-only profile but adds a genuinely new fact — no credit consumption — and discloses the returned content. It stays quiet on pagination/error behavior for a nonexistent ID.

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 short sentences, front-loaded with the core action and no filler. Opening 'Get list by ID' mildly duplicates the title, which costs a point but nothing is wasted.

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?

A one-parameter, read-only lookup with no output schema; the description covers what is returned (status, progress, count) and the safety/credit profile, which is enough for an agent to call it correctly. Only the ID-discovery path is left implicit.

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 0%, but there is a single nested string parameter (list_id) described as 'List ID'. The description adds only 'by its ID', so it does not compensate for the zero coverage — though the parameter is nearly self-evident. Baseline 3.

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 (Get/Retrieve) and resource (list by ID) and enumerates what the payload contains (build status, progress, total count). This distinguishes it clearly from the plural dealmachine_get_lists and from dealmachine_get_lists_list_id_items, though it never names those siblings.

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?

Usage is only implied: reaching for this tool when you already have a list_id and want its detail. There is no explicit when-to-use, when-not-to-use, or alternative named (e.g. use get_lists to discover IDs first, use ..._items to fetch members).

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