fizzy_list_columns

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

No annotations are provided, so the description must carry the full burden. It only states 'list all columns' without disclosing any behavioral details such as read-only nature, pagination, ordering, error handling, or response format. This is minimal and provides no extra context beyond the name and schema.

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 is front-loaded with the action and resource. Every word earns its place, and there is no unnecessary filler.

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?

This is a simple one-parameter tool, so the description is largely adequate. However, without an output schema or annotations, the description does not clarify the return format (e.g., column objects, names, ordering) or any potential edge cases. For a low-complexity tool, this is acceptable but not fully 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?

Schema description coverage is 100% for board_id, which is described as 'The ID of the board'. The description adds minimal extra meaning by connecting board_id to the board whose columns are listed, but this is effectively redundant. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'List all columns on a Fizzy board' uses a specific verb ('list') and resource ('columns') with a clear scope ('on a Fizzy board'). It clearly distinguishes from siblings like fizzy_list_cards and fizzy_list_boards by naming the specific resource being listed.

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 (when you need to list columns on a board) but does not provide explicit guidance on when to use this tool versus siblings or any exclusions. There are no alternatives for listing columns among siblings, so a simple implication may suffice, but it lacks explicit context.

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