listCustomFields

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

There are no annotations, so the description bears the full burden. It does disclose useful pagination behavior (default 10 per page, limit=100 to fetch all), but it omits other behavioral details like return shape, ordering, or whether any permissions are required.

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 front-loaded sentence: it states the purpose first, then immediately provides pagination guidance. Every word earns its place with no filler or repetition.

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 paginated list tool, the description is mostly adequate. However, the lack of output schema and the existence of listDealCustomFields as a sibling create a scope ambiguity that the description does not resolve, leaving some completeness gap.

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 descriptions already cover both parameters, but the description adds practical value by explaining that limit=100 fetches all in one call, leveraging the max 100 constraint. This goes beyond the schema and gives the agent actionable invocation guidance.

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 'List custom fields' with a specific verb and resource. However, it does not distinguish this from the sibling tool listDealCustomFields, leaving potential ambiguity about whether these are person-level custom fields.

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 alternatives like listDealCustomFields, createCustomField, or getCustomField. The only actionable note is about pagination, which is not a usage-context guideline.

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