itglue_list_flexible_asset_fields

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

With no annotations, the description carries full burden. It discloses the return content (trait keys, kinds, required) but does not mention pagination behavior, error conditions, or performance implications. Adequate but not rich for a read-only list tool.

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 main purpose is front-loaded. The description is a single sentence with useful details and synonyms. Slightly verbose with synonyms but still efficient and structured well.

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?

Covers the return value (trait keys, kinds, required) and workflow placement. No output schema exists, so the description compensates. Missing error handling or pagination details, but complete enough for a simple list operation.

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 100%, so baseline is 3. The description adds no extra semantic meaning to parameters; it only mentions return fields. No value added beyond the input 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?

The description clearly states the verb (List) and resource (schema/custom field definitions for a specific flexible asset type). Synonyms and workflow placement further distinguish it from sibling tools like itglue_list_flexible_asset_types and itglue_create_flexible_asset.

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 sequencing: 'Call AFTER itglue_list_flexible_asset_types and BEFORE itglue_create_flexible_asset / itglue_update_flexible_asset'. This tells the agent exactly when to use this tool relative to others, which is excellent guidance.

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