get_field_values

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

With no annotations, the description carries full behavioral disclosure burden. It only states the basic action, omitting details like authentication requirements, whether the operation is read-only, or what the output format contains (though an output schema exists, the description adds no context on pagination or field selection).

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 sentence, making it concise and front-loaded. However, it is too minimalist, lacking important details that could have been added without verbosity, which reduces its overall effectiveness.

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 the tool's simplicity and the existence of an output schema, the description still falls short. It does not clarify what 'custom field values' includes, whether it returns all fields or a subset, or how it relates to sibling tools like list_custom_fields. The context is insufficient for an agent to use it confidently.

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 description coverage is 0%, meaning the description does not explain the contact_id parameter. While the schema defines it as required, the description adds no meaning beyond 'for a contact', leaving interpretation to the agent. A low coverage demands compensation which is absent.

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 'Get all custom field values for a contact' clearly states the verb (get), resource (custom field values), and scope (for a contact), distinguishing it from sibling tools like list_custom_fields (which lists available fields) and set_field_value (which writes).

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like list_custom_fields or set_field_value, nor does it mention any prerequisites or limitations.

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