listDealCustomFields

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

With no annotations provided, the description carries the burden of disclosing behavior. It discloses pagination behavior (default 10, pass limit=100 to fetch all), which is useful. However, it does not explicitly state it is a read-only operation or mention any side effects, authentication, or rate limits. The pagination note is a partial contribution 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?

The description is a single, focused sentence that front-loads the purpose and immediately provides actionable pagination guidance. There is no redundant information, making it highly concise and well-structured.

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 list tool with no output schema and two optional parameters, the description is adequately complete. It covers the essential behavior (pagination) and provides a concrete tip. It does not describe the response structure, but that is not strictly necessary given the tool's simplicity and lack of output 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?

Schema coverage is 100% with descriptions for both limit and offset. The description adds value by recommending limit=100 to fetch all in one call, offering practical guidance beyond the schema's basic parameter descriptions. This is a helpful tip, so it exceeds the baseline of 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?

The description clearly states the tool lists deal custom fields, which is a specific verb+resource. However, it does not explicitly distinguish from sibling tools like listCustomFields or listDeals, so while the purpose is unambiguous, it lacks explicit differentiation.

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 implies usage for listing deal custom fields but provides no when-to-use guidance or exclusions. The mention of pagination is a usage hint for handling large datasets, but it does not explain when to prefer this over alternatives or when not to use it.

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