list_deal_custom_fields

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

No annotations are provided, so the description carries the full burden. It discloses the default limit override (100 vs. 10), the presence of _metadata, and how pagination works. It does not explicitly state read-only behavior, but 'List' implies it, and the pagination details add useful behavioral insight beyond the schema.

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, all useful. The purpose is front-loaded, the endpoint is given, and pagination instructions follow. No filler or 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 no output schema and no annotations, this description covers the critical operational details: what it lists, the pagination behavior, and how to proceed when more results exist. The mention of cursor-based endpoints like notes is slightly tangential but still helps the agent handle similar tools. Nothing essential is missing for correct invocation.

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, but the description adds value by explaining the limit default and how to use offset/cursor for pagination. It also hints at extraQuery usage with an example, which enriches the parameter meaning beyond the bare schema.

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 all deals custom fields') and includes the endpoint (GET /dealCustomFields). It clearly distinguishes this from the sibling list_custom_fields by restricting scope to deal custom fields, so an agent can tell them apart without opening schemas.

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?

It gives clear context on when pagination is needed ('bulk requests are the common case') and explains how to paginate with offset or cursor. It does not explicitly name alternatives (e.g., get_deal_custom_field for a single field), but the scope is obvious from the name and description.

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