list_custom_meta_fields

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

With no annotations available, the description carries the full burden of behavioral disclosure. It only says 'List' and does not mention that this is a read-only operation, whether pagination is needed for large result sets, how results are ordered, or what fields are returned.

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 concise sentence with no unnecessary words, but it is under-specified. It could include useful context without becoming verbose, such as noting that it returns a paginated list or that the query parameter searches by name/description.

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 moderate complexity (optional search and pagination) and the presence of sibling tools like get_custom_meta_field and export_custom_meta_fields, the description is incomplete. It does not explain the scope of the listing, the response format, or how it relates to other metadata field tools.

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 covers all three parameters (q, page, per_page) with descriptions, so schema coverage is 100%. The description adds no additional meaning beyond what the schema already provides, such as how the search query interacts with pagination or the default behavior when parameters are omitted.

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 the action (list) and resource (custom metadata fields), which is specific and distinguishes it from get_custom_meta_field (singular). However, it does not specify the scope (e.g., all fields) or mention the search/pagination options, leaving some ambiguity about the tool's full capabilities.

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 guidance is provided. The description does not indicate when to use this tool versus alternatives like get_custom_meta_field or export_custom_meta_fields, nor does it mention any prerequisites or typical scenarios.

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