swapcard_get_select_field_options

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

No annotations are provided, so the description carries the burden. It states the tool returns definitions and option values, which is a read operation, but it doesn't disclose any additional behavioral traits like pagination, rate limits, or whether it returns all fields or only those with options. The description is adequate but not rich.

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 that front-loads the key information. No wasted words.

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?

The tool has only one parameter and no output schema, so the description is relatively complete for a simple read operation. However, it doesn't mention what the response looks like or any edge cases (e.g., what happens if no select fields exist). Given the simplicity, a 3 is appropriate.

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%, so the description must compensate. It mentions 'eventId' implicitly by context but doesn't explain the parameter's meaning or format. The description adds some value by specifying the resource type (Select/MultipleSelect custom fields) but doesn't detail the eventId parameter beyond what the schema shows.

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 tool retrieves Select and MultipleSelect custom field definitions with option values, which is specific and distinguishes it from sibling tools like swapcard_get_custom_fields (which likely retrieves all custom fields). However, it doesn't explicitly name the sibling tool for comparison.

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 implies usage for fetching select-type custom field options, but it doesn't explicitly state when to use this tool versus swapcard_get_custom_fields or other alternatives. No exclusions or prerequisites are mentioned.

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