listDealCustomFields

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

With no annotations, the description must disclose behavioral traits, but it only restates the tool name. It does not mention whether this is a safe read operation, pagination, sorting, return format, or any other behavioral details, providing zero transparency.

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 extremely short but it is essentially a paraphrase of the tool name, offering no additional information. It is under-specified rather than concise, omitting crucial details about the output and 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?

With no annotations, no output schema, and only a sparse description, the tool context is significantly incomplete. It does not explain what 'deal custom fields' are (e.g., definitions vs. values), how they are returned, or any limits, leaving the agent without enough information.

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 tool has zero parameters, so there is no parameter behavior for the description to explain. The schema confirms no inputs are required; the baseline of 4 applies here since no parameter information is necessary.

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 uses a specific verb ('List') and resource ('deal custom fields'), clearly indicating it retrieves deal custom fields. However, it does not distinguish itself from the sibling tool 'listCustomFields', leaving potential ambiguity about the scope of the listing.

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 is provided on when to use this tool versus the similarly named 'listCustomFields' or other sibling tools. There is no mention of prerequisites, use cases, or exclusions, leaving the agent without context for selecting this tool.

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