cm_get_custom_fields

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

The description discloses that the tool reads custom fields, consistent with the readOnlyHint annotation. However, it adds no additional behavioral context such as required permissions, rate limits, or response structure.

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, clear sentence that front-loads the action and resource. There is no unnecessary information, making it efficient and easy to parse.

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 read-only tool with one parameter, the description covers the essential purpose. However, it could be enhanced by mentioning the return format or what constitutes a custom field. Given the simplicity, it is mostly complete.

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 input schema has one parameter (listId) with a minimal description. The tool description does not elaborate on the parameter's meaning or how to obtain it. Since schema coverage is 100%, the description adds no extra semantics, resulting in a baseline score 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 uses the specific verb 'Get' and resource 'all custom fields defined on a list,' clearly indicating the tool's function. It distinguishes itself from sibling tools like cm_create_custom_field, cm_delete_custom_field, and other list gets by explicitly naming the resource.

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 does not provide any guidance on when to use this tool versus alternatives. It simply states the action, leaving usage to be implied by the name and context. No explicit when-not or alternative references are given.

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