list_custom_fields

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

Describes output as schema (name, type, options) and explicitly states it does NOT return values. No annotations exist, but description covers behavior sufficiently for a read-only tool. Lacks mention of authentication or rate limits, but that's expected.

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?

Two sentences, front-loaded with purpose and entity types. No unnecessary words. Highly efficient.

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?

Low complexity tool with one parameter and no output schema. Description fully covers what it does, what it returns, and how it differs from sibling tools. No gaps.

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?

Input schema has one parameter with full description. The description adds useful context: 'Use kases for projects.' This clarifies the enum value mapping beyond 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?

Clearly states it lists custom field definitions for entity types (parties, opportunities, kases). Distinguishes from value retrieval tools like get_party, get_opportunity, get_project by explicitly stating it returns schema, not values.

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?

Provides explicit when to use (inspect schema) and when not (to read values on a record). Directs users to alternative tools (get_party with embed=fields) for value retrieval.

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