list_all_custom_fielddata_field_values

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

The description confirms read-only behavior and no side effects, which aligns with annotations. It adds context about the endpoint and that it deals with deal data. However, it doesn't mention pagination or rate limits, though annotations already provide 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 very concise, front-loading the read-only indicator and endpoint. Every sentence adds value without redundancy.

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 5 parameters including pagination and filters, the description is minimal. It doesn't explain pagination or filtering behavior, but the schema covers parameters adequately. Output format is not described, but no output schema exists.

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%, so baseline is 3. The description adds no parameter-specific information beyond what the schema already provides.

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 reads deal custom field values. It uses a verb ('List') and a resource ('custom field values'). However, it does not differentiate this tool from similar sibling tools like 'list_all_custom_field_values' or 'list_all_custom_field_values_2'.

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?

No guidance on when to use this tool versus alternatives. There are many similar list tools among siblings, but the description provides no criteria for selection.

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