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

The description mentions boards are filtered by the caller's API key, which is a behavioral trait. However, it does not disclose pagination, ordering, or what the output contains (though output schema exists). No annotations are provided, so the description carries full burden but is minimal.

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 sentence with no unnecessary words. It is front-loaded with the essential information: action and scope.

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 no parameters and the presence of an output schema, the description is largely complete. It could mention that the list may be empty or that it includes all boards without pagination, but it is sufficient 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?

There are no parameters, so the schema coverage is 100%. The description does not need to add parameter details. It appropriately implies no filtering or options, which is clear.

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 it lists boards, specifying the scope ('available to the caller's FeatureJet API key'). It distinguishes from the sibling 'get_board' (singular) by implying a list vs. a single board, but does not explicitly differentiate from other board-related tools.

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 explicit guidelines on when to use this tool versus alternatives like 'get_board' or 'publish_board'. The usage is implied: to retrieve all boards accessible by the API key. 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.